From owner-freebsd-questions@FreeBSD.ORG  Wed Oct  8 17:07:26 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EA3CF16A4B3
	for <freebsd-questions@freebsd.org>;
	Wed,  8 Oct 2003 17:07:26 -0700 (PDT)
Received: from munk.nu (mail.munk.nu [213.152.51.194])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 34FE843F93
	for <freebsd-questions@freebsd.org>;
	Wed,  8 Oct 2003 17:07:26 -0700 (PDT)	(envelope-from munk@munk.nu)
Received: from munk by munk.nu with local (Exim 4.24; FreeBSD 4.8)
	id 1A7OKz-0005l4-65
	for freebsd-questions@freebsd.org; Thu, 09 Oct 2003 01:07:25 +0100
Date: Thu, 9 Oct 2003 01:07:25 +0100
From: Jez Hancock <jez.hancock@munk.nu>
To: freebsd-questions@freebsd.org
Message-ID: <20031009000725.GA21291@users.munk.nu>
Mail-Followup-To: freebsd-questions@freebsd.org
References: <20031008113325.B11482@asu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031008113325.B11482@asu.edu>
User-Agent: Mutt/1.4.1i
Sender: User Munk <munk@munk.nu>
Subject: Re: cvsup and portupgrade
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Oct 2003 00:07:27 -0000

On Wed, Oct 08, 2003 at 11:33:25AM -0700, David Bear wrote:
> 
> I'm still trying to muddle through the loads of different ways to keep
In addition to the other good advice given in this thread - when you get
used to portupgrade remember to edit /usr/local/etc/pkgtools.conf.
This file allows you to specify how portupgrade behaves when upgrading
ports matching a pattern, say like 'www/mod_php4'.

For example if you use mod_php4 and opt to run portupgrade on that port
once a week, generally you will be told that the port is 'out of date',
since the mod_php4 is updated generally once every few days.

However if you allow portupgrade to just upgrade mod_php4 as it sees
fit, it will not by default rebuild the port with all the options you
chose originally.  

To get around this you can include options in
/usr/local/etc/pkgtools.conf to specify which features you want mod_php4
to be built with when modified using portupgrade or portinstall, saving
the hassle of having to 'make clean deinstall' and then 'make install'
again, selecting all the options you want manually.


-- Jez Hancock
 - System Administrator / PHP Developer

http://munk.nu/