You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
) For node-build, we had need to support a different default mirrored URL scheme. In doing so, we have extended the mirror support to not only accept a *_MIRROR_URL environment variable, but also to accept a *_MIRROR_CMD variable with the name of a function or command which can construct a full mirrored package URL (given the original package URL and checksum as arguments). In this manner, node-build can default to a common mirror scheme for node mirrors, but also be flexible enough to allow users to construct URLs as necessary for their specific mirror sites.
We haven't yet merged this feature into node-build. If everything goes as planned and it is merged to node-build, I intend to also submit this feature here to ruby-build. In hopes of gathering feedback ahead of time, I would love some comments on this feature.
The text was updated successfully, but these errors were encountered:
Currently, the mirror supported by rbenv and ruby-build has a customized directory structure.
The mirror url format is
$RUBY_BUILD_MIRROR_URL/$checksum
but not like
$RUBY_BUILD_MIRROR_URL/2.3/ruby-2.3.1.tar.bz2
It means that I can't download ruby from any existing "plain mirror". I have to make my own "custom mirror" for ruby-build. For example, there are some ruby mirrors (ruby-china & ustc) in mainland China, but Chinese users cannot use ruby-build to download ruby from there.
A Chinese developer has written an rbenv plugin called rbenv-china-mirror to solve this problem. But I think it's just a hack. This problem should be solved by ruby-build.
At present, ruby-build only supports the
mirrorUrl/checksum
format for mirrored package URLs. (ruby-build/bin/ruby-build
Line 356 in ffef606
The core of this feature is in nodenv/node-build@c73fbe2 as part of nodenv/node-build#210
We haven't yet merged this feature into node-build. If everything goes as planned and it is merged to node-build, I intend to also submit this feature here to ruby-build. In hopes of gathering feedback ahead of time, I would love some comments on this feature.
The text was updated successfully, but these errors were encountered: