Public SourceMage Discussion List

[Sukneet Basuta <sukneet AT gmail.com>]

On Sun, Feb 17, 2013 at 4:14 PM, David Kowis <dkowis AT shlrm.org> wrote:
> tl;dr : Don't use SOURCEFORGE_URL any longer, sourcforge.net has their
> own mirror system; make sure your urls start with
> http://downloads.sourceforge.net/; Fix spells as you come across them.
>
>
> So our SOURCEFORGE_URL mirror system is very broke :(
>
> Basically, all references to SOURCEFORGE_URL need to be replaced with
> the project specific urls that project uses on sourceforge.net. They
> have their own geo-ip based load distributing, and mirroring is handled
> automatically now, unlike in the past.
>
> So there's no particularly good way to use SOURCEFORGE_URL, since most
> of the path is project specific, and may or may not match the spell name.
>
> Also, there's no particularly good way to go through and replace it for
> all spells. I have written a ruby script that takes advantage of
> capybara and selenium to attempt to scrape the download path from the
> project itself, it's not 100% accurate, but it can help automate some of
> the mess away.
>
> The results of that execution are here: http://sprunge.us/iUPV
> Format of the results is:
> status|spell|url|${SOURCE} (as in SOURCE from DETAILS)
>
> Statuses:
> SUCCESS: able to wget a file from the url, and the end of the url
> matches SOURCE
> FILE: able to weget a file from a scraped url, but the end doesn't match
> SOURCE
> FAILURE: couldn't find a project on sf.net by the spell name
>
> Obviously, there's a few shortcomings in this method, as there's no
> guarantee that the spell name matches the project name, as well as there
> might be multiple files associated with that project, and the default
> one might not be the one desired.
>
> Perhaps I'll work on making this a bit more robust, but for the most
> part, individual spells need to be fixed as they are come across.
>

If we are just going to use downloads.sourceforge.net, why not just
change SOURCEFORGE_URL to default to that?
downloads.sourceforge.net/${PROJECT_NAME}/${SOURCE} works perfectly
and spell maintainers don't have to fix anything.

If we are going to include the actual path for the file, I think we
should still use SOURCEFORGE_URL and default that to
downloads.sourceforge.net, but also allow the user to select the
mirror. i.e. 
downloads.sourceforge.net/project/easystroke/easystroke/0.5.6/easystroke-0.5.6.tar.gz
or
switch.dl.sourceforge.net/project/easystroke/easystroke/0.5.6/easystroke-0.5.6.tar.gz

But anyway, I think my first suggestion is the easiest and probably
the best right now.