I'll n-th that. Gentoo's emerge is great. I have a few redhat and a
mandrake system that I'm having to take care of, and rpm type stuff just
makes me want to bang my head against something, or choke the xxx out of
some redhat packager that desperately needs it. The proverbial rpm
dependency hell makes me want to go back to being a technopeasant.
glibc upgrades have not been a problem that I have been aware of.
Mostly the minor ones Just Happen. Emerge has an option (emerge -e
world) to recompile the whole machine (more or less, that can be a
gotcha) -except- the glibc specifically so that you can be sure that
everything is compiled for the same glibc. So what I'll do if I see a
.x glibc rev, I'll recompile glibc, then do the 'emerge -e world'
option.
Truth in Enthusiasm principles do force me to confess Gentoo is not
trouble-free however. Most of the time it's sloppy emerge packaging.
Sometimes other things. And there is lots of informally documented
tediousness that can make things work significantly better. And there's
lots and lots and lots of out-of-date or obsolete tediousness that can
take you down a rabbit trail dead end. But overall, it's a whole lot
easier to make Gentoo sing and dance the way I want it to than any other
distro I've worked with (caveat, I haven't done the LFS thing yet. Real
Life gets in the way of so much important stuff....)
On Sat, Nov 06, 2004 at 11:10:36PM +0000, Justin Dieters
<enderak@mtaonline.net> wrote:
> I third it. Gentoo's emerge is great. In fact, once you install any
> gentoo system, there is no real reason to upgrade to a newer release,
as=20
> emerge will give you the same updated packages as a newer version.
How does gentoo handle major glibc upgrades? I've always been a
slackware user, but my installed glibc is so old that I can't use
up-to-date binary packages. (And no, I can't upgrade glibc -- I tried.)
I'm planning to switch to gentoo, and the question I'm asking now is how
distributions handle major glibc upgrades. I don't want to switch to
another distro and end up with the same long-term maintainability
problem.
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Mon Nov 8 07:58:49 2004
This archive was generated by hypermail 2.1.8 : Mon Nov 08 2004 - 07:58:49 AKST