Projects with multiple versions in our ports tree

[Oliver Eikemeier]

Doug Barton wrote:

> On Sun, 15 Aug 2004, Jun Kuriyama wrote:
>
>> Ade wrote:
>
>>> One thing that slightly bugs me are ports that effectively include the
>>> version number twice, for example:
>>>
>>> 	cd /usr/ports/dns/bind9 && make -V PKGNAME
>>> 	bind9-9.2.3
>>>
>>> To my mind, that should really read bind-9.2.3, with appropriate
>>> LATEST_LINK magic.
>>
>> Agreed.
>
> The problem here was that I had users who wanted to be able to do 
> 'pkg_add -r bind9' and have something useful happen. :)  This is 
> another reason why I wanted to have "fooNN" be the real ports, and 
> "foo" be a slave port, or what have you.

Index: dns/bind9/Makefile
===================================================================
RCS file: /home/ncvs/ports/dns/bind9/Makefile,v
retrieving revision 1.58
diff -u -u -r1.58 Makefile
--- dns/bind9/Makefile	4 Apr 2004 06:19:46 -0000	1.58
+++ dns/bind9/Makefile	15 Aug 2004 14:24:28 -0000
@@ -11,7 +11,7 @@
  # version. If you are concerned about using the most recent ISC
  # release you can generally build it cleanly from the source - Doug

-PORTNAME=	bind9
+PORTNAME=	bind
  PORTVERSION=	9.2.3
  CATEGORIES=	dns net ipv6
  MASTER_SITES=	${MASTER_SITE_ISC}
@@ -21,6 +21,8 @@
  MAINTAINER=	DougB at FreeBSD.org
  COMMENT=	Completely new version of the BIND DNS server

+LATEST_LINK?=	${PKGNAMEPREFIX}bind9${PKGNAMESUFFIX}
+
  # ISC releases things like 9.2.2rc1, which our versioning doesn't like
  ISCVERSION=	9.2.3


-Oliver