From owner-freebsd-ports@FreeBSD.ORG Tue Apr 3 19:46:10 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00F1B16A404 for ; Tue, 3 Apr 2007 19:46:10 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id D007A13C44C for ; Tue, 3 Apr 2007 19:46:09 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 1391A519CC for ; Tue, 3 Apr 2007 15:46:04 -0400 (EDT) Date: Tue, 3 Apr 2007 20:45:59 +0100 From: RW To: freebsd-ports@freebsd.org Message-ID: <20070403204559.08345338@gumby.homeunix.com> In-Reply-To: <461275DC.20408@debtresolve.com> References: <461275DC.20408@debtresolve.com> X-Mailer: Claws Mail 2.8.1 (GTK+ 2.10.11; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Ports tree infrastructure 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, 03 Apr 2007 19:46:10 -0000 On Tue, 03 Apr 2007 11:42:20 -0400 Dan Casey wrote: > I am having trouble finding documentation that goes in more detail > then that of the handbook. I am sending this message in hopes that > you may be able to point me in the right direction, or know of a > better way to accomplish this. > > I am setting up a single server as a 'build box' for our freebsd > servers. We want to build our own packages because > 1. we may need to compile certain ports with different flags then > freebsd chooses. > 2. We want to update ports only when needed. Ie: Unless we need > something in a new version of a port, or unless there is a security > hole, we want to keep the old version. > > What I'm setting up is a regular ports tree (/usr/ports) which is Not > updated. Then a second tree /usr/local/current-ports which is updated > daily with portsnap. > > When I want to upgrade a port, I would copy it over from the current > ports tree. I'm not sure what to do about the INDEX files, which is > what i had trouble finding documentation on. You can build your own with make index; or just ignore it, it's only used by a few minor targets and the tools in the portupgrade package. A more serious problem is that eventually a new port may not work in the old ports infrastructure. As far as security is concerned it's probably easier just to incorporate a patch into the old port - see the porters' handbook.