LATEST_LINK not in index

[Pav Lucistnik]

Dominic Fandrey píše v st 01. 04. 2009 v 00:12 +0200:

> > Upgrades are easy. Look up @comment ORIGIN line in +CONTENTS file of the
> > port being upgraded, then look up this value in second column of INDEX
> > file.
> > 
> 
> I don't see how this is connected to my question.
> 
> I want people to be able to use LATEST_LINK to identify ports,
> e.g. apache for www/apache13, apache20 form www/apache20 and so
> forth. LATEST_LINK is a unique identifier, unfortunately
> neither recorded in the INDEX nor +CONTENTS.
> Also, to read it from +CONTENTS (if it were there) I'd have to
> know, which package is actually meant, which I don't know,
> because this is the information I want to find out.

Maybe you really want people to specify ports by ORIGIN, not by
LATEST_LINK ...

-- 
Pav Lucistnik <pav at oook.cz>
              <pav at FreeBSD.org>

You can't expect to wield supreme executive power just 'cause some
watery tart threw a sword at you.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
	=?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?=
	=?ISO-8859-1?Q?_zpr=E1vy?=
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20090401/5eeccb54/attachment.pgp