From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Time to move on?
Date: Sun, 22 Mar 2009 10:27:29 +0200 [thread overview]
Message-ID: <200903221027.29803.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <200903212350.05253.mdiehl@diehlnet.com>
On Sunday 22 March 2009 07:50:04 Mike Diehl wrote:
> So here is the question: Are these just growing pains, or is this the
> trend with Gentoo? If I resolve to update frequently, will these problems
> become more rare?
I've been using Gentoo for 4 years now, my main desktop is still running code
that I compiled on the first install in 2005. And I'm on my third Gentoo
notebook in a row. Absurb update issues simply don't happen, as long as you
follow the rules:
Update weekly on <~arch>
Update monthly on <arch>
Adjust to suit your needs.
You ran into the mktemp issue, which feels about a year old from this corner,
so Iguess you have not been updating regularly. I'm not sure where you got the
advice to update only when you need a new feature or a fix, but it is not
workable in practice.
Gentoo does have issues, but the majority of them are with changes to
packages, not changes to Gentoo. Remember that with Gentoo you are rebuilding
a live system on the actual system itself. We don't have build farms that
rebuild the entire distro and push out new rpms nightly - so the problems that
can hit Gentoo don't happen to binary distro users.
Take expat. It got an upgrade a long time ago which coudl break Gnome entirely
if you didn't do it right. There was nothing the devs could do really, because
that's how those packages were written. The normal case is to have a bare
machine, build expat, then build Gnome. On Gentoo, you want to do all of this
while using the Gnome that needs to be rebuilt. If you update regularly,
you'll find lots of people around who know what the steps are and can help.
Today, most of us have forgotten and need to turn to Google to find the
howtos.
If you find this happens more and more often with gentoo, it is probably a
symptom of more and more useful packages out there, that are being developed
faster with more features. See it as a sign of success on the part of FLOSS
rather than a failing of Gentoo.
And I would advise AGAINST gentoo on your out-of-state servers. They need too
much pampering to keep them stable. I have about 100 machines at work, a
mixture of 30% FreeBSD, SuSE <ugh>, some Centos and even a single lone Solaris
machine. The worst of the lot has to be the SVN server, running Gentoo. No-one
will touch it anymore, and the last time I did, I broke it horribly with a
conflict between portage and cpan Perl modules.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-03-22 8:29 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 1:17 [gentoo-user] Time to move on? Mike Diehl
2009-03-22 2:17 ` Mike Kazantsev
2009-03-22 3:00 ` Dale
2009-03-22 5:50 ` Mike Diehl
2009-03-22 6:31 ` Dale
2009-03-22 8:27 ` Alan McKinnon [this message]
2009-03-22 8:34 ` Neil Bothwick
2009-03-22 9:13 ` KH
2009-03-22 6:58 ` Philip Webb
2009-03-22 8:26 ` Neil Bothwick
2009-03-22 11:37 ` Philip Webb
2009-03-22 11:52 ` Neil Bothwick
2009-03-22 18:56 ` James Homuth
2009-03-22 19:46 ` Dale
2009-03-22 19:46 ` Dale
2009-03-22 9:17 ` emerge-log (was: Re: [gentoo-user] Time to move on?) Daniel Pielmeier
2009-03-22 7:01 ` [gentoo-user] Re: Time to move on? Francesco Talamona
2009-03-22 11:44 ` [gentoo-user] " Peter Alfredsen
2009-03-22 14:48 ` Albert Hopkins
2009-03-22 13:07 ` Dirk Heinrichs
2009-03-22 13:18 ` Damian
2009-03-22 20:23 ` Mark Knecht
2009-03-22 20:45 ` Neil Bothwick
2009-03-22 22:02 ` Mark Knecht
2009-03-22 23:02 ` Neil Bothwick
2009-03-23 0:26 ` Dale
2009-03-23 0:53 ` Neil Bothwick
2009-03-23 3:18 ` Dale
2009-03-23 3:39 ` Albert Hopkins
2009-03-23 23:58 ` Dale
2009-03-24 0:42 ` Hilco Wijbenga
2009-03-24 5:20 ` Dale
2009-03-24 2:34 ` Albert Hopkins
2009-03-24 2:46 ` James Skinner
2009-03-24 6:32 ` Dale
2009-03-24 8:01 ` Daniel Pielmeier
2009-03-24 9:32 ` [gentoo-user] Time to move on? -> top posting KH
2009-03-24 8:53 ` [gentoo-user] Time to move on? Neil Bothwick
2009-03-25 1:40 ` Stroller
2009-03-25 1:54 ` Neil Bothwick
2009-03-25 3:49 ` Dale
2009-03-25 10:40 ` Neil Bothwick
2009-03-25 11:09 ` Dale
2009-03-25 11:27 ` James Skinner
2009-03-25 12:14 ` Neil Bothwick
2009-03-25 12:16 ` Saphirus Sage
2009-03-25 14:54 ` Momesso Andrea
2009-03-25 14:14 ` Alan McKinnon
2009-03-25 15:16 ` Paul Hartman
2009-03-25 15:21 ` Paul Hartman
2009-03-25 18:10 ` Alan McKinnon
2009-03-25 21:41 ` Graham Murray
2009-03-26 0:38 ` Dale
2009-03-26 7:08 ` Momesso Andrea
2009-03-25 7:06 ` Alan McKinnon
2009-03-25 21:24 ` [gentoo-user] Time to move on? - snippage Stroller
2009-03-25 21:39 ` AllenJB
2009-03-25 21:56 ` Roy Wright
2009-03-25 17:39 ` [gentoo-user] Re: Time to move on? Christer Ekholm
2009-03-23 8:53 ` [gentoo-user] " Neil Bothwick
2009-03-26 15:04 ` [gentoo-user] Re: aliases Thanasis
2009-03-27 5:32 ` Dale
2009-04-03 5:47 ` Thanasis
2009-04-03 6:39 ` Dale
2009-03-22 20:55 ` [gentoo-user] Time to move on? Albert Hopkins
2009-03-22 22:07 ` Mark Knecht
2009-03-22 23:20 ` Stroller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903221027.29803.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox