From owner-freebsd-ports@FreeBSD.ORG  Tue Apr  3 16:42:49 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: 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 1707D16A404
	for <ports@freebsd.org>; Tue,  3 Apr 2007 16:42:49 +0000 (UTC)
	(envelope-from dcasey@debtresolve.com)
Received: from debtresolve.com (ip175-18.wp-ny-us.debtresolve.com
	[66.236.175.18])
	by mx1.freebsd.org (Postfix) with ESMTP id D118A13C4B9
	for <ports@freebsd.org>; Tue,  3 Apr 2007 16:42:48 +0000 (UTC)
	(envelope-from dcasey@debtresolve.com)
Received: from dummy.name; Tue, 03 Apr 2007 11:42:47 -0400
Message-ID: <461275DC.20408@debtresolve.com>
Date: Tue, 03 Apr 2007 11:42:20 -0400
From: Dan Casey <dcasey@debtresolve.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: ports@FreeBSD.org
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Ports tree infrastructure
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Apr 2007 16:42:49 -0000

    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.

This looks like it is going to be a pain to maintain this.  Are there
any ports or scripts that pointy hat uses that could be helpful in my
type of environment.   Are there any better solutions?