On Wed, 8 Feb 2012 00:11:26 +0700
Pandu Poluan <pa...@poluan.info> wrote:
> On Feb 7, 2012 2:39 PM, "Eray Aslan" <e...@gentoo.org> wrote:
> >
> > On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote:
> > > Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?
> >
> > Yes, it should be OK as long as you run
> > etc-update/dispatch-conf/similar after the upgrade. Postfix
> > daemons now live under /usr/libexec/postfix (not
> > under /usr/lib{,64)/postfix). Adjust your main.cf accordingly.
> > I'll add a warning to the ebuild.
> >
>
> Ah, thanks for the explanation!
>
> I'll be certain to pay undivided attention to postfix ebuild warnings.
>
> Rgds,
ALWAYS pay special attention to ALL ebuild warnings. Not just the ones
from postfix.
Those warnings are there for a reason - it's how devs let you know that
stuff has changed, that the change will make stuff break, and how to
fix or prevent it. They are not there for decoration or fluff.
You should set the ELOG options in make.conf to store these warnings in
some persistent place (log files, mail them, whatever) so you can go
through them at your leisure.
My usual routine for doing a global update is
emerge -avuND world
conf-update
emerge -av @preserved-rebuild
revdep-rebuild -p -i (then without -p if something is found)
emerge -a --depclean
view portage logs and do what they say
often followed by doing one or more steps again to ensure all is clean
I haven't been adversely hit by an upgrade for over a year now. I put
it down to using the portage tools correctly in the way they were
designed to be used.
--
Alan McKinnnon
alan.mckin...@gmail.com
