at the moment the following Apache versions are available in "pkgsrc": - Apache 1.3.41 is in "pkgsrc/www/apache". - Apache 2.0.63 is in "pkgsrc/www/apache2". - The one true Apache 2.2.10 is in "pkgsrc/www/apache22". This is IMHO wrong considering that all version older than 2.2.0 are legacy version as far as the Apache foundation is concerned. I would therefore like to re-arrange the package like this: - Apache 1.3.41 will be moved to "pkgsrc/www/apache13". - Apache 2.0.63 will be moved to "pkgsrc/www/apache20". - Apache 2.2.10 will be moved to "pkgsrc/www/apache". I think the pain of renaming (and breaking 'make update', and definitely pkg_rollin-replace operation) is greater than the pain of this confusion, especially because the descriptions can be clear in DESCR which version is best is a matter of opinion anyway. I concur that we should leave apache22 as apache22. I don't care very 1much if we rename apache to apache13 or not. For packages which have only one version in pkgsrc at a time, it's reasonable to leave off the version. Once we have muliple versions at once, I think all packages should get the version, and once a package seems to need this we should stay even if we later dropped apache13 and apache20, because surely apache24 is coming.
Description: PGP signature