From owner-freebsd-questions@FreeBSD.ORG  Sat Oct 29 19:07:51 2011
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 197C6106566B
	for <freebsd-questions@freebsd.org>;
	Sat, 29 Oct 2011 19:07:51 +0000 (UTC)
	(envelope-from doug@safeport.com)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
	by mx1.freebsd.org (Postfix) with ESMTP id CD14D8FC0A
	for <freebsd-questions@freebsd.org>;
	Sat, 29 Oct 2011 19:07:50 +0000 (UTC)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1])
	by fledge.watson.org (8.14.4/8.14.4) with ESMTP id p9TJ7mjW097509;
	Sat, 29 Oct 2011 15:07:48 -0400 (EDT)
	(envelope-from doug@safeport.com)
Received: from localhost (doug@localhost)
	by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id
	p9TJ7lXH097497; Sat, 29 Oct 2011 15:07:47 -0400 (EDT)
	(envelope-from doug@safeport.com)
X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs
Date: Sat, 29 Oct 2011 15:07:47 -0400 (EDT)
From: doug@safeport.com
X-X-Sender: doug@fledge.watson.org
To: Polytropon <freebsd@edvax.de>
In-Reply-To: <20111029195804.f876fcff.freebsd@edvax.de>
Message-ID: <alpine.BSF.2.00.1110291417580.44429@fledge.watson.org>
References: <j8grps$3m3$1@dough.gmane.org>
	<201110291401.08722.jmc-freebsd2@milibyte.co.uk>
	<CAGyFPjJui6POBSu=gX-SBBy7ksMAH3eu9NRqPuiSnH5RVjUbJg@mail.gmail.com>
	<20111029195804.f876fcff.freebsd@edvax.de>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3
	(fledge.watson.org [127.0.0.1]);
	Sat, 29 Oct 2011 15:07:48 -0400 (EDT)
Cc: Mike Clarke <jmc-freebsd2@milibyte.co.uk>,
	Huub van Niekerk <huubvanniekerk@gmail.com>, freebsd-questions@freebsd.org
Subject: Re: update packages by pkg_add
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: doug@fledge.watson.org
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: Sat, 29 Oct 2011 19:07:51 -0000

On Sat, 29 Oct 2011, Polytropon wrote:

> On Sat, 29 Oct 2011 17:53:28 +0200, Huub van Niekerk wrote:
>> Thank you for your answer. But how about if the package-to-be-replaced is a
>> dependency? Just remember the dependency and do the same ?
>
> As you're going to reinstall the package immediately,
> there won't be a problem. Of course, a depending program
> won't properly run until you've actually replaced the
> package in question.
>
> For keeping track of dependencies, you can also use
> portmaster or portupgrade and use -P and -PP options
> to work with packages (like pkg_add does) instead of
> compiling from sources. The "pkgdb -aF" command will
> properly store dependency informations.

If you are not familiar with portmaster or portupgrade, I would see if 
portmaster would do what you want. It is written in shell script and uses the 
underlying package/port files. For me it has worked well as long as I do not try 
to update KDE. Two other packages that are very helpful in updating are pkg_tree 
and pkg_cleanup. In addition, if part of your problems are perl, python and 
maybe php, there are make.conf variables to specify (in effect) that the 
versions installed should meet any dependency requirements. portdowngrade is 
very helpful if you have a component that is newer than what you need. I needed 
this to install kdiff3 a while ago.