Date: Tue, 3 Apr 2007 20:45:59 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Ports tree infrastructure Message-ID: <20070403204559.08345338@gumby.homeunix.com> In-Reply-To: <461275DC.20408@debtresolve.com> References: <461275DC.20408@debtresolve.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 03 Apr 2007 11:42:20 -0400 Dan Casey <dcasey@debtresolve.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070403204559.08345338>