On Tue, Nov 11, 2008 at 6:37 AM, Chad Woolley <[EMAIL PROTECTED]> wrote: > > > On Mon, Nov 10, 2008 at 9:53 PM, Tom Copeland <[EMAIL PROTECTED]> wrote: >> >> The RubyForge file downloads are more or less round-robined between the >> various mirror servers... I say "more or less" because some server are >> handed more requests than others. But all the mirrors should be serving all >> files after the rsync'ing process has finished... > > That doesn't appear to be the case. For example, this link is still valid: > > http://rubyforge.org/frs/download.php/43985/rubygems-1.3.0.tgz > > However, this one (manually edited to point to 1.3.1) is not: > > http://rubyforge.org/frs/download.php/43985/rubygems-1.3.1.tgz > > I can only download 1.3.1 if I use this different mirror (linked from the > rubygems files page): > > http://rubyforge.org/frs/download.php/45905/rubygems-1.3.1.tgz > > ...which means I had to update the URL in my scripts. > > Regardless, even if the 43985 mirror worked for 1.3.1, it still wouldn't be > enough to make scripts stable because: > > 1. A currently-valid mirror could go offline in the future > 2. There is still no generic url to grab the "latest" without hardcoding the > version in the url - which means scripts must still be updated even if all > mirrors worked and stayed around forever. >
45905 like 43985 (for 1.3.0) refers to the release package in GForce software, is not a permanent URL that you can reference. We deal the same while updating rubyinstaller scripts. -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams _______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
