At 2008-08-26T16:37:28+08:00, joeb wrote: > Why does the AUTOCONFxxx change the suffix between Freebsd releases?
>From `/usr/ports/UPDATING': 20070930: AFFECTS: everyone AUTHOR: Mark Linimon <[EMAIL PROTECTED]> The ports tree has been migrated to the latest version of autoconf, 2.61. Versions 2.53 and 2.59 were declared obsolete and removed. > In 6.2 it was called AUTOCONF259 in 7.0 its called AUTOCONF261. Is > this not a violation of the naming convention? The ports names are > not suppose to carry the version number as part of its name. I assume the convention you are referring to is from the Porter's Handbook [5.2.5, Package Naming Conventions]: Otherwise, the PORTNAME should not contain any version-specific information. It is quite normal for several ports to have the same PORTNAME, as the www/apache* ports do; in that case, different versions (and different index entries) are distinguished by the PKGNAMEPREFIX, PKGNAMESUFFIX, and LATEST_LINK values. There is no violation of this convention in this case: % make -C /usr/ports/devel/autoconf261 -V PORTNAME autoconf In any case, the conventions are not followed strictly. For instance, the above section of the Porter's Handbook says, "The first letter of the name part should be lowercase." However, % make -C /usr/ports/graphics/ImageMagick -V PKGNAME ImageMagick-220.127.116.11 Raghavendra. -- N. Raghavendra <[EMAIL PROTECTED]> | http://www.retrotexts.net/ Harish-Chandra Research Institute | http://www.mri.ernet.in/ See message headers for contact and OpenPGP information. _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"