On Feb 11, 2010, at 19:01, Scott Haneda wrote:
> And I also note that there is "projects" and "files" in that name as well,
> which makes me completely unable to understand how "sourceforge:assp" works?
> Internally, I am not at all understanding what is going on. I have had this
> as a suggestion:
> master_sites
> sourceforge:"assp/${name}%20Installation/${name}%20${version}/"
> Which works, but I certainly do not like it.
>
> And I just tried:
> master_sites sourceforge:assp
> Of course, it works, but I swear I tried it before, with correct case, and it
> was not working.
>
> When I go to http://assp.sourceforge.net/ and click on downloads, and am
> taken to:
> http://sourceforge.net/projects/assp/files/
>
> I see the main link is a download with this resource:
> http://sourceforge.net/projects/assp/files/ASSP%20Installation/ASSP%201.6.5.4/ASSP_1.6.5.4-Install.zip/download
>
> How in the heck does MacPorts go from sourceforge:assp to that url? What is
> the real and full url MacPorts is going to expand that to. You can ignore
> the FQDN part of it (since there are so many mirrors), I am looking to know
> the URI that is expanded.
>
> Is this a convention, to put :projectname in the master_sites, and if so, how
> would I know, or determine this on my own, with nothing more than the urls to
> the project.
Yes, that is the convention, for master_sites definitions like sourceforge,
gnu, googlecode, etc. See:
http://guide.macports.org/#reference.phases.fetch
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
