Re: Re: Ok. Heh, is there still an smtp-based list out here:D

2007/2/1, Bill Barry <[email protected]>:
>
>
> > Yeah, whenever I get some upgraded power hardware I'll probably try
> > Gentoo
> > again. But taking a whole day to compile openoffice (several times in a
> > month) is just not feasible. That particular collection of programs
> might
> > become more modular over time but there's always something else huge
> > to take its place. Things are done very different in various distros
> > though,
> > so some experiences might not help at all, but it at least gives a more
> > general knowledge of the linux way of doing things!
> Try a KDE full recompile (at least a day on my system).
>
> If you stick to the stable tree (+x86), things don't come out quite as
> often (but the compiling takes longer, because you have to do more at
> any given time) and the system is actually stable (I can't remember the
> last time I have managed to crash something). Combine that with a
> nightly cronjob to update everything except the largest packages (I do
> kde and oo on fridays at 10:30pm on one system and sundays at 1am on
> another) and you don't have to think about having a system that is ever
> obsolete or updating while you are using it.


Nice idea Bill, care to mail me that script? How do you deal with
compilation errors?

You don't actually have to wait while updating your system, as some people
seem to think. I run my updates in a minimized terminal in KDE, so I can
just continue using the system. Also, because you're in an X gui, you can
use a graphical diff program to update your config files, which works
wonders for me.

Gentoo is still the linux distro I keep returning to, even with the long
build times. If things go seriously wrong, it's Portage package management
is the only one that won't stand in my way while fixing it. But yes, it
takes a while, and some manual/forum reading, to feel comfortable with.

Tools that ease my update burden; cfg-update: for easier config file
updating, ccache: to cache compiled sourcecode (also makes it less
troublesome to just kill an update process  and resume later), elogviewer:
to view output from compilations at a later stage, an easy to understand
graphical diff between config files.

Greetings, Yggdrasil