On Saturday 28 June 2008, Philip Webb wrote:
> > your manually maintained log is entirely redundant if you emerge
> > Genlop
>
> How so ? -- the site given by 'eix genlop' simply goes on re Perl.
emerge genlop.
When it runs it essentially parses /var log/emerge.log and gives output
like so:
Sat Jun 28 22:09:53 2008 >>> dev-util/git-1.5.6.1
Sat Jun 28 22:12:28 2008 >>> x11-themes/qtcurve-0.59.3
Sat Jun 28 22:14:30 2008 >>> x11-themes/qtcurve-qt4-0.59.4
The benefit is that there is no chance to accidentally omit recording an
update if you do it manually.
> > and by telling portage to log to disk there is no real need
> > to sit glued to the screen watching console output anymore.
>
> I know: I have 280 MB in /var/log/emerge-logs (wry smile).
>
> Anyway, I've just done my weekly update. There were 4 pkgs to
> process -- eselect-ctags fetchmail autoconf shared-mime-info -- &
> also eix , which has a new version in testing (safe enough for eix).
> Of course, I make use of Konsole tabs to facilitate eix & emerge,
> update 'pkg.ref' with Gvim running on another KDE desktop
> & use Klipper to copy info between Konsole & Gvim.
>
> I've been doing it this way for nearly 8 years
> & have never run into a serious problem: HTH one or two others
> (smile).
:-)
I prefer to just let the software do what it's best at - mindless
execution of instructions - and I get on with what I'm best at - not
mindlessly executing instructions. I figure that if an emerge fails, it
will do so with identical output whether I use emerge world or emerge
package. If an ebuild outputs important warnings and/or info it's in
the log file where I can examine it at leisure. I've never yet seen a
case where emerge package would have left me in a better position than
emerge world intelligently used. The closest case was expat, but
nothing in the emerge procedure would have prepared me for the result
of that - one had to emerge it to then discover the resulting breakage.
These days we have @preserved-rebuild to handle even that.
I guess we all have our favoured way of doing updates.
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
[email protected] mailing list
