From owner-freebsd-ports@FreeBSD.ORG Mon Nov 21 20:59:12 2005 Return-Path: X-Original-To: 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 39BF816A421 for ; Mon, 21 Nov 2005 20:59:12 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dukecmmtao02.coxmail.com (dukecmmtao02.coxmail.com [68.99.120.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77D7B43D66 for ; Mon, 21 Nov 2005 20:59:11 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by dukecmmtao02.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051121205925.PTLW6953.dukecmmtao02.coxmail.com@dns1>; Mon, 21 Nov 2005 15:59:25 -0500 From: Vizion To: Wesley Shields Date: Mon, 21 Nov 2005 12:59:07 -0800 User-Agent: KMail/1.8 References: <200511210839.56424.vizion@vizion.occoxmail.com> <20051121191335.GA56240@csh.rit.edu> In-Reply-To: <20051121191335.GA56240@csh.rit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211259.08340.vizion@vizion.occoxmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: UPDATING - needs updating? 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: Mon, 21 Nov 2005 20:59:12 -0000 On Monday 21 November 2005 11:13, the author Wesley Shields contributed to the dialogue on- Re: UPDATING - needs updating?: >On Mon, Nov 21, 2005 at 08:39:55AM -0800, Vizion wrote: >> Hi >> >> I have noticed that some earlier notices relating to some ports in >> UPDATING appear as though they have been made out of data by newer notices >> (e.g kde 20050804 seems to replace 20050324) and sometimes the >> instructions conflict with one another. While I presuime the latest notice >> always takes precedence I wonder if it would be possible to have notices >> that are no longer current removed from UPDATING. > >I think this is probably a bad idea, simply from a historical >perspective. If I wanted to chase down a bug that was available only >for a specified time period I would like to know the corresponding >UPDATING entries. My focus comes from the primary purpose of UPDATING - to help check the best way to update one's own ports(e.g the info on kde). Hence scanning a list of ports affected by UPDATING at the time of updating does seem best suited for that purpose and I wonder if the non current data might therefore be better shifted to something like UPDATING.history to fulfill the very real need you identify. > >> I know I would find it useful to have an html version of UPDATING with an >> index page by port with a link to the notices. How easy it would be to do >> this automatically as UPDATING is upfated I do not know but I throw the >> idea out there in case anyone feels like catching it. > >I believe freshports.org can do this already, though backwards. Rather >than looking through UPDATING for links to the individual ports you can >find the corresponding entries in the individual ports themselves (see >www.freshports.org/x11/xterm as an example). Yep I am aware of that - but backwards is not what is needed in the contect od using UPDATING when updating one's systems. I see the hml index list as enabling one to scan the list of ports referred to on UPDATING and use that index to extract the information relevant to one's own system(s). my two pennorth -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit.