versioned ports naming convention

[Bjoern A. Zeeb]

On Thu, 10 Jul 2003, Oliver Eikemeier wrote:

Hi,

> just a quick question:
>
> When there are multiple versioned ports (like www/apache13
> and www/apache2) PORTNAME shouldn't be versioned (i.e. apache),
> that's how I understand the FreeBSD Porter's Handbook,
> 4.2.4 Package Naming Conventions:
> <http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-naming.html#PORTING-PKGNAME>
>
> Examples are:
> mail/cyrus-imapd, mail/cyrus-imapd2 and mail/cyrus-imapd22
> security/cyrus-sasl and security/cyrus-sasl2
> mail/exim-old, mail/exim
> devel/autoconf, devel/autoconf213, devel/autoconf253, devel/autoconf257
> devel/automake, devel/automake14, devel/automake15, devel/automake17
>
> Now Christian Kratzer told me that this policy is about to change:
> <http://lists.freebsd.org/pipermail/freebsd-ports/2003-July/002646.html>
>
> Did I misinterpret the porter's handbook or do I overlook the advantages
> of having versioned PORTNAMEs?

not policy I think but commiter's choice.

I did have another one: xerces-c2. PORTNAME originally had been set to
xerces_c as had and still has xerces-c port.

It got committed with PORTNAME = xerces-c2.

I think this comes from dir name == PORTNAME thinking and I liked it
for one thing: from what I can think of fixing dependencies with
multiple concurrent versions is easier ?


Nevertheless there should be a consensus amongst porters and commiters
throughout the whole tree and an explicit note to porters-guide I think.

Have a poll ? ;-)

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/