From owner-freebsd-stable@FreeBSD.ORG Tue Dec 20 10:25:15 2005 Return-Path: X-Original-To: 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 3FB7816A41F for ; Tue, 20 Dec 2005 10:25:15 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from raven.kierun.org (raven.yorksj.ac.uk [193.61.234.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id D665343D45 for ; Tue, 20 Dec 2005 10:25:12 +0000 (GMT) (envelope-from yann@raven.kierun.org) Received: from yann by raven.kierun.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EoegC-0000rX-RO; Tue, 20 Dec 2005 10:25:12 +0000 Date: Tue, 20 Dec 2005 10:25:12 +0000 From: Yann Golanski To: rihad Message-ID: <20051220102512.GA2952@kierun.org> References: <43A7A3F7.7060500@mail.ru> <20051220083913.GA505@kierun.org> <43A7DA65.1020801@mail.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43A7DA65.1020801@mail.ru> User-Agent: Mutt/1.5.11 Sender: "Yann Golanski, University of York, +44(0)1904-433088" Cc: freebsd-stable@freebsd.org Subject: Re: ports security branch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2005 10:25:15 -0000 Quoth rihad on Tue, Dec 20, 2005 at 14:18:13 +0400 > A very interesting script for its own purpose, but I'm afraid this > doesn't answer my question at all. Perhaps seeing the way that e.g. > Debian deals with the upgrade problem might shed some light on the > issue. Hell, FreeBSD does exactly that for the base world+kernel, too! > Not for the ports, though. As far as I know, the way to keep up to date with ports is to follow the procedure: portaudit -Fad if no_problems then quit else cd /usr/ports make update portupgrade port1 port2 port3 (...) If you want to do that automatically, put my script (or a similar one) into cron but that way lies pain. You've been warned. -- yann@kierun.org -=*=- www.kierun.org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318