From owner-freebsd-ports@FreeBSD.ORG Tue Nov 22 18:26:35 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 BA3F216A41F for ; Tue, 22 Nov 2005 18:26:35 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7CE743D60 for ; Tue, 22 Nov 2005 18:26:15 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 95F82D12350 for ; Tue, 22 Nov 2005 13:26:14 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Tue, 22 Nov 2005 13:26:14 -0500 X-Sasl-enc: 4np2oig5KAAGj69CmezsYuzm6QytssVFJanKFs5qYGsP 1132683973 Received: from gumby.localdomain (88-104-206-120.dynamic.dsl.as9105.com [88.104.206.120]) by frontend2.messagingengine.com (Postfix) with ESMTP id BA44B571416 for ; Tue, 22 Nov 2005 13:26:13 -0500 (EST) From: RW To: freebsd-ports@freebsd.org Date: Tue, 22 Nov 2005 18:26:01 +0000 User-Agent: KMail/1.8.3 References: <200511210839.56424.vizion@vizion.occoxmail.com> In-Reply-To: <200511210839.56424.vizion@vizion.occoxmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511221826.13118.list-freebsd-2004@morbius.sent.com> 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: Tue, 22 Nov 2005 18:26:36 -0000 On Monday 21 November 2005 16:39, 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 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. UPDATING is essentially a journel that describes the pitfalls associated with continously keeping your ports up-to-date. You need to follow the directions from the time of your last update to the current date. If you update so infrequently that you accumulate several entries that apply to the same port, you need to use your common sense about home to combine them. The only meaningful way to do that is to read them in order. I just run a script that shows a diff between the current version and the previous version. If you update frequently you only see one or two entries at a time, and many can be ignored - particularly if you update with portmanager.