Date: Mon, 29 Aug 2011 11:10:08 -0400 From: Chris Brennan <xaero@xaerolimit.net> To: freebsd-ports@freebsd.org Subject: Re: MASTER_SITE_SOURCEFORGE: how do *you* handle it? Message-ID: <4E5BABD0.9090300@xaerolimit.net> In-Reply-To: <20110828210511.3d2e0604@cox.net> References: <20110828210511.3d2e0604@cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig162BE095E4E3961AA7E6E36E Content-Type: multipart/mixed; boundary="------------020504000704020102070705" This is a multi-part message in MIME format. --------------020504000704020102070705 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 8/28/2011 10:05 PM, Conrad J. Sabatier wrote: > I'm wondering how other ports maintainers are dealing with their=20 > definitions of MASTER_SITES=3D, DISTFILES=3D, DISTNAME=3D, etc. with > regards to Sourceforge. >=20 > In browsing a number of projects recently on Sourceforge, I've > noticed that the paths to project distfiles are now using the > element "projects" rather than "project". >=20 > What I'm looking for is how to declare things in a clean and elegant=20 > fashion in a port's Makefile to handle these cases, one that will=20 > hopefully not require any revisions for later upgrades. Is it > necessary to just scrap the "SF" definition entirely and hardcode the > URL? >=20 > In addition, I've run across a few projects that use slightly > differing versions of the project name, either somewhere in the path > or for the distfile name itself. For example, looking at the > "scidvspc" project earlier today, I noticed this: >=20 > The link for the distfile is defined as: >=20 > http://sourceforge.net/projects/scidvspc/files/source/scid_vs_pc-4.5.tg= z/download > > Clicking the download link, one is presented with alternatives in > case the download doesn't start automatically. >=20 > The "mirror" link: >=20 > https://sourceforge.net/settings/mirror_choices?projectname=3Dscidvspc&= filename=3Dsource/scid_vs_pc-4.5.tgz > > The "direct link": >=20 > https://downloads.sourceforge.net/project/scidvspc/source/scid_vs_pc-4.= 5.tgz?r=3D&ts=3D1314582468&use_mirror=3Dsuperb-sea2 > > Frankly, I'm baffled as to how our current definition of=20 > "MASTER_SITES=3DSF/<something>" is supposed to handle all of this. >=20 > Can anyone point me towards a source of enlightenment? :-) >=20 > Thanks! >=20 Slightly related and unrelated at the same time. So sorry if I drifted too far. I was discussing this very concept about a month ago with a friend. I was trying to update my PortableApps.om installation and the script I had written to fetch updated apps broke because I couldn't figure out how to handle these new url's. It would see SF's idea of a direct link is a redirect, thus obfuscating the real servers even more and the path the project is in.... --=20 > Chris Brennan -- A: Yes. >> Q: Are you sure? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting frowned upon? > http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/=20 > GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) ------------------------------------------------------------------------ --------------020504000704020102070705-- --------------enig162BE095E4E3961AA7E6E36E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOW6vXAAoJEO7NmoTVsgwM0/oH/1IV5lTptFG0ArHqwGJ/0hnz RGuUGTU+DcJWYeppWFihjGlwjWpM/vRJ/gkRdve/HLv9kzeZBV8P4pA4+dg3lh0d 4o8VtVpFQfM5fff/y2MW/Dy3N2YG5J4lBdOIjXDYTtIdYrT26dlv7E5H/nWIa+RB TnpJG3lmULNHPxW7K/wBZcNHx7GviGmIulAXcPpzoeeLx+K0jvF8Sy8B9VLhDiJm DXx0tPCXXp5rOmslIobcRoSN37g4ehxTq+TdBZ4yDHEg9KAV4zdeMgA/4UIJWvga tyg2zxgS+iFcdfuvyotE0vKZTwG7OIX1p7HMbHhnsd8ysCPSF6OOSmIYQ/hV1b4= =RvHP -----END PGP SIGNATURE----- --------------enig162BE095E4E3961AA7E6E36E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E5BABD0.9090300>