Date: Tue, 20 Dec 2005 10:25:12 +0000 From: Yann Golanski <yann@kierun.org> To: rihad <rihad@mail.ru> Cc: freebsd-stable@freebsd.org Subject: Re: ports security branch Message-ID: <20051220102512.GA2952@kierun.org> In-Reply-To: <43A7DA65.1020801@mail.ru> References: <43A7A3F7.7060500@mail.ru> <20051220083913.GA505@kierun.org> <43A7DA65.1020801@mail.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051220102512.GA2952>