Date: Tue, 9 Nov 2010 23:40:47 +0200 From: Dmitry Pryanishnikov <lynx.ripe@gmail.com> To: Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Combining several upgrades using portmaster Message-ID: <AANLkTi=-epBdykkQ7%2BHQwBzqFzPK6RR%2B1MrP38off-3O@mail.gmail.com> In-Reply-To: <20101109193017.GA45046@wep4035.physik.uni-wuerzburg.de> References: <AANLkTi=vv-d2dz8aJUkoNYObbiSV%2ByXPNnnkzVeVZREK@mail.gmail.com> <4CD98299.9090809@FreeBSD.org> <20101109193017.GA45046@wep4035.physik.uni-wuerzburg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! 2010/11/9 Alexey Shuvaev <shuvaev@physik.uni-wuerzburg.de>: > In the case that you catch 2 or more sweeping updates it is very likely > that you are updating across rather large time interval (half of a year > or more). In this case I usually ignore all '-r' UPDATING entries and > do just portmaster -a. The idea is that almost all ports have got > updated in this large period of time too. I routinely use 'portmaster -a' on my workstation. OTOH for a server machine '-r gettext' and '-r png-' may be less disrupting: it won't touch ports for running server processes (e.g. squid or bind), and thus prevent service downtime during the upgrade. I prefer to upgrade ports for such a server processes only when absolutely necessary (e.g. when they become vulnerable), and not just on port version change (which will trigger an upgrade when using 'portmaster -a'). -- Sincerely, Dmitry nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=-epBdykkQ7%2BHQwBzqFzPK6RR%2B1MrP38off-3O>