Date: Fri, 03 Apr 2009 11:46:39 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: pav@FreeBSD.org Cc: freebsd-ports@FreeBSD.org Subject: Re: LATEST_LINK not in index Message-ID: <49D5DAFF.9030304@bsdforen.de> In-Reply-To: <1238573306.66242.1.camel@pav.hide.vol.cz> References: <49CE6B06.8080402@bsdforen.de> <1238446459.17527.4.camel@hood.oook.cz> <49D2956A.20106@bsdforen.de> <1238573306.66242.1.camel@pav.hide.vol.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Pav Lucistnik wrote: > 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 ... > Actually I want people to be able to do both. Since this is a binary package only tool, I want people to be able to use the same parameters as they'd be able to use with "pkg_add -r". I have implemented some guessing by now and it fails very rarely. But it's not the kind of solution I like.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49D5DAFF.9030304>