From owner-freebsd-ports@FreeBSD.ORG Tue Mar 31 22:13:02 2009 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1458E106566B for ; Tue, 31 Mar 2009 22:13:02 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id A03AF8FC21 for ; Tue, 31 Mar 2009 22:13:01 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [88.130.221.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 0F30C8A00D1; Wed, 1 Apr 2009 00:12:59 +0200 (CEST) Message-ID: <49D2956A.20106@bsdforen.de> Date: Wed, 01 Apr 2009 00:12:58 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.21 (X11/20090321) MIME-Version: 1.0 To: pav@FreeBSD.org References: <49CE6B06.8080402@bsdforen.de> <1238446459.17527.4.camel@hood.oook.cz> In-Reply-To: <1238446459.17527.4.camel@hood.oook.cz> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Cc: freebsd-ports@FreeBSD.org Subject: Re: LATEST_LINK not in index X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 22:13:02 -0000 Pav Lucistnik wrote: > Dominic Fandrey píše v so 28. 03. 2009 v 19:23 +0100: > >> I'm working on a binary package upgrade tool that gets all required >> information from the INDEX file downloadable from the package >> repositories. This means you do not need a local copy of the ports >> tree to use it. >> >> The only information required and missing is the LATEST_LINK. >> Normally this is easily done by stripping the package name of >> the version, but some ports define a proprietary LATEST_LINK >> to avoid conflicts. This leads to the following problem, my >> program has to do some guessing and in these cases it fails: >> >> # pkg_upgrade firefox3 >> # >> >> # pkg_upgrade firefox >> www/firefox;firefox-2.0.0.20_4,1 >> www/firefox3;firefox-3.0.7,1 >> # >> >> It either matches none or more than one port. I could build >> some guessing logic, but the real solution would be to have >> the LATEST_LINK name in the index file. Is there any chance >> a LATEST_LINK column will be added if I file a PR? > > 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.