From owner-freebsd-ports@FreeBSD.ORG  Mon Aug 23 22:37:55 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4E57C16A4CE
	for <ports@freebsd.org>; Mon, 23 Aug 2004 22:37:55 +0000 (GMT)
Received: from fillmore.dyndns.org (port-212-202-50-15.dynamic.qsc.de
	[212.202.50.15])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 19D0D43D1D
	for <ports@freebsd.org>; Mon, 23 Aug 2004 22:37:55 +0000 (GMT)
	(envelope-from eikemeier@fillmore-labs.com)
Received: from dhcp-10.local ([172.16.0.10])
	by fillmore.dyndns.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.41 (FreeBSD))
	id 1BzNRo-0005ug-9S; Tue, 24 Aug 2004 00:37:54 +0200
Date: Tue, 24 Aug 2004 00:37:57 +0200
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
To: "Dan Langille" <dan@langille.org>
From: Oliver Eikemeier <eikemeier@fillmore-labs.com>
In-Reply-To: <412A1B18.4785.80649D9F@localhost>
Message-Id: <14C14956-F555-11D8-8CAA-00039312D914@fillmore-labs.com>
Content-Transfer-Encoding: 7bit
User-Agent: KMail/1.5.9
cc: ports@freebsd.org
Subject: Re: LATEST_LINK unique or not?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Aug 2004 22:37:55 -0000

Dan Langille wrote:

> Is LATEST_LINK supposed to be unique? It's not. There's about 201
> ports which have duplicate values.

It is, expect when NO_LATEST_LINK is set (in which case no latest link 
exists). Did you filtr out these cases? Everything else is bug, Kris did 
some survey AFAIK.

-Oliver