From owner-freebsd-vuxml@FreeBSD.ORG Thu Sep 23 23:46:40 2004 Return-Path: Delivered-To: freebsd-vuxml@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AF9316A4CE; Thu, 23 Sep 2004 23:46:40 +0000 (GMT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0445C43D4C; Thu, 23 Sep 2004 23:46:40 +0000 (GMT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 2F8D13D37; Thu, 23 Sep 2004 19:46:31 -0400 (EDT) From: "Dan Langille" To: "Jacques A. Vidrine" Date: Thu, 23 Sep 2004 19:46:31 -0400 MIME-Version: 1.0 Message-ID: <41532817.15157.4F01E691@localhost> Priority: normal In-reply-to: <20040922201538.GC57256@madman.celabo.org> References: <20040921192821.K69630@xeon.unixathome.org> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: freebsd-vuxml@freebsd.org Subject: Re: FreshPorts beta now displays VuXML data X-BeenThere: freebsd-vuxml@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documenting security issues in VuXML List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 23:46:40 -0000 On 22 Sep 2004 at 15:15, Jacques A. Vidrine wrote: > On Tue, Sep 21, 2004 at 07:35:20PM -0400, Dan Langille wrote: > > Hi, > > > > I just finished the first cut of the code that marks commits as affected > > by VuXML data. Have a look at your favourite VuXML entry and see if the > > associated package is affected. > > > > e.g. http://beta.freshports.org/?package=pine > > Thanks, Dan! I've experimentally added links on VuXML.org pages to > FreshPorts URLs like the one above. Thus, if you click on a package > name at say > http://vuxml.freebsd.org/e9f9d232-0cb2-11d9-8a8a-000c41e2cdad.html > it will probably have you looking at the right FreshPorts entry. That looks good. I hope that type of linking makes it easier for others to link. FWIW, I am making progress on the VuXML issues. I have found that I need to set historical PORTEPOCH for all ports that have a PORTEPOCH [1]. By historical, I mean for each commit in FreshPorts. That's the only way I can then get a proper test result from 'pkg_version - t. I'm almost there. This page http://beta.freshports.org/tmp/epoch-fetching-slave.txt (500KB) lists the ports that have a PORTEPOCH, the commits for that port, and the historical value of the PORTEPOCH value for that commit. I do this by literally fetching each revision of the Makefile. FreshPorts knows that revision is associated with each commit (that information is in the cvs-all email0. Obtaining the PORTEPOCH values is not a simple grep command. You must do a "make -V PORTVERSION". There are 27 ports containing an EPOCH value that are also slave ports. Of these 27, two set their own EPOCH value, the other 25 get it from the MASTERPORT. It is thoese 25 ports which are going to be tougher. There are 15 distinct master ports involved (fortunately, none of them have their own MASTERPORTs). I'm not yet sure how I'm going to cope with these master ports. The others should be straight forward. [1] FWIW, there are 246 ports with a PORTEPOCH value. This differs from the result of this command, perhaps because not all such ports are in the INDEX I'm using (e.g. archivers/bsdtar) awk -F\| '$1 ~ /,/ {print $2 "/Makefile"}' /usr/ports/INDEX- -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/