Hi, Marc Espie wrote on Sun, Oct 02, 2011 at 10:22:52AM +0200: > On Sun, Oct 02, 2011 at 12:28:09AM +0200, Ingo Schwarze wrote:
>> - The naming is terrible, one is not even versioned, but i will talk >> to Kristaps to fix that before the next mandoc-tools release. > Bad Kristaps. ;-) Obviously not used to work as an upstream developer > for packagers. > > In the meantime, use DIST_SUBDIR, as everyone who has to deal with unversioned > distfiles does... Thanks for the hint. Is the following correct an wanted? Yours, Ingo -- The casual porter is the best frequent asker. Index: guide.html =================================================================== RCS file: /cvs/www/faq/ports/guide.html,v retrieving revision 1.13 diff -u -r1.13 guide.html --- guide.html 21 Nov 2010 10:26:03 -0000 1.13 +++ guide.html 2 Oct 2011 10:27:37 -0000 @@ -193,13 +193,17 @@ Ports normally correspond to given versions of software. Once they are retrieved, files are checksummed and compared to the recorded checksum(s) in distinfo. So, to avoid confusion, DISTFILES and PATCHFILES should have clearly visible version numbers: don't retrieve foo-latest.tar.gz if it is a link to foo-1.0.5.tar.gz. -If necessary, gently ask the original program author to make such -distinctions clear. +If one of these files is only available with an unnumbered name, +gently ask the original program author to make such distinctions clear. +In the meantime, if you must use an unnumbered distribution file, +set DIST_SUBDIR to what a reasonable DISTNAME would be, like foo-1.0.5, +such that different, identically named versions of the distfile do not +clash on the distribution file mirrors. <li> If a given port needs more than about 5 DISTFILES + PATCHFILES to work, use DIST_SUBDIR to avoid cluttering DISTDIR (/usr/ports/distfiles by default) too much. -<li> -DIST_SUBDIR must not include version numbers. When the port is updated to a later version, some distfiles may not change, but will be +In this case, DIST_SUBDIR must not include version numbers. When the port +is updated to a later version, some distfiles may not change, but will be refetched if DIST_SUBDIR is changed. Even if all distfiles change, it is easier for the user to track cruft. <li> All DISTFILES and PATCHFILES don't necessarily come from the same set of MASTER_SITES. Supplementary sites can be