From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Anxiousness? [was:Tips/Tricks for Gentoo on low-spec computer?]
Date: Tue, 20 Jan 2009 14:47:18 -0600 [thread overview]
Message-ID: <58965d8a0901201247w4f8229cbib4d5451adb39e9b@mail.gmail.com> (raw)
In-Reply-To: <497635EA.8070908@gmail.com>
On Tue, Jan 20, 2009 at 2:36 PM, b.n. <brullonulla@gmail.com> wrote:
> Mark Knecht ha scritto:
>
>> The one thing I would respectfully suggest is that you carefully
>> build your own portage overlay. My experience with Gentoo over the
>> last few years is that there is a _anxiousness_ in the portage
>> maintainer area to move newer revisions of software into portage
>> quickly and then just as quickly to remove from portage what users are
>> currently using.
>
> Really?
>
> I am usually a bit annoyed by the contrary. On an almost 1-year old
> Kubuntu (8.04 Hardy Heron) I can find packages that are just barely x86
> stable now on Gentoo.
>
> A couple of examples I am aware of:
> Firefox 3: stable just since one month on Gentoo x86, was included in KB8.04
> Qtiplot: 0.9.x stable and working on KB8.04, all releases ~x86 (and a
> hell to compile on a stable system -still didn't manage to do it) in Gentoo.
>
> Python releases are often behind, and not mentioning KDE 4, which is
> even default on 8.10 Kubuntu and on Gentoo was still hardmasked last
> time I checked (but probably Gentoo is just right in this respect,
> everyone keeps telling me to wait before digging into KDE 4).
>
> I fully understand that there are good reasons for that, and that the
> meta-distribution status of Gentoo makes harder to check packages (and
> also that the Ubuntu folks wildly release unstable stuff... firefox 3 rc
> in 8.04, for example). I just feel that (stable) Gentoo is actually a
> bit *behind* the average Linux distribution in its revisions of software.
>
> Most importantly, I also feel that that's something new: when I first
> installed my system, more than 4 years ago, I felt it was *ahead*. I
> wonder if it's due just to the sheer increase of work required to test
> packages, or if there are decisions behind that (or if it's just me
> having false memories).
When I first installed Gentoo a few years ago, I think I switched from
x86 to ~x86 in the first 24 hours, for the very reason. I wanted to
use the newest versions and the "stable" stuff was so old... It seems
the majority of users are using ~arch these days.
next prev parent reply other threads:[~2009-01-20 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 16:46 [gentoo-user] Tips/Tricks for Gentoo on low-spec computer? Grant Edwards
2009-01-20 17:05 ` Paul Hartman
2009-01-20 17:11 ` Nick Cunningham
2009-01-20 17:36 ` [gentoo-user] " Grant Edwards
2009-01-20 17:38 ` [gentoo-user] " Mark Knecht
2009-01-20 20:36 ` [gentoo-user] Anxiousness? [was:Tips/Tricks for Gentoo on low-spec computer?] b.n.
2009-01-20 20:47 ` Paul Hartman [this message]
2009-01-20 21:16 ` Nick Cunningham
2009-01-20 21:33 ` Saphirus Sage
2009-01-21 0:28 ` Peter Alfredsen
2009-01-20 18:01 ` [gentoo-user] Tips/Tricks for Gentoo on low-spec computer? Dirk Heinrichs
2009-01-20 19:30 ` [gentoo-user] " Grant Edwards
2009-01-20 18:09 ` [gentoo-user] " kashani
2009-01-21 0:50 ` Dale
2009-01-24 14:40 ` Steven Lembark
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=58965d8a0901201247w4f8229cbib4d5451adb39e9b@mail.gmail.com \
--to=paul.hartman+gentoo@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