From owner-freebsd-stable@FreeBSD.ORG  Tue Dec  7 15:56:19 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0884416A4CE
	for <freebsd-stable@freebsd.org>;
	Tue,  7 Dec 2004 15:56:19 +0000 (GMT)
Received: from virtual.micronet.sk (smtp-r.micronet.sk [213.215.96.238])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0C88C43D5C
	for <freebsd-stable@freebsd.org>;
	Tue,  7 Dec 2004 15:56:14 +0000 (GMT)
	(envelope-from danger@wilbury.sk)
Received: from DANGER ([213.215.105.189])
	by virtual.micronet.sk (8.12.11/8.12.11) with ESMTP id iB7FtVT0053332;
	Tue, 7 Dec 2004 16:55:32 +0100 (CET)
	(envelope-from danger@wilbury.sk)
Date: Tue, 7 Dec 2004 16:53:34 +0100
From: DanGer <danger@wilbury.sk>
X-Mailer: The Bat! (v3.0.1.33) Professional
X-Priority: 3 (Normal)
Message-ID: <1775779333.20041207165334@wilbury.sk>
To: Ivan Voras <ivoras@fer.hr>, freebsd-stable@freebsd.org
In-Reply-To: <41B5D08B.1070608@fer.hr>
References: <41B5D08B.1070608@fer.hr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Large port updates
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: DanGer <danger@wilbury.sk>
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Dec 2004 15:56:19 -0000

Hi Ivan,

Tuesday, December 7, 2004, 4:47:23 PM, you Cannot open file "C\TXT COOKIES\reply-en.txt":

> Is there a "best practice" for automated updating large number of 
> interdependant ports? I keep my ports tree up-to-date, and sometimes I
> wish to install applications that depend on a newer version of an 
> existing one, and fail.

> My current example is gnome. Recently, whatever I want to install 
> requires gnome2.8 - how to update the giant list of gnome libs & apps?
> portupgrade -r? (but on what package?)

portupgrade -arR should be good...

> What about ports that have dialog boxes which require user intervention?

i don't know exactly, you have to watch and see what's happening..

-- 
Best regards

+----------==/\/\==----------+             FreeBSD
| DanGer <danger@wilbury.sk> |     (__)    The
| DanGer@IRCnet ICQ261701668 |  \\\'',)    Power
| http://danger.homeunix.org |    \/  \ ^  To
+----------==\/\/==----------+    .\._/_)  Serve

[ If idiots could fly this place would be an airport. ]