From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gnome 2.26 stable?
Date: Tue, 29 Sep 2009 21:46:00 -0400 [thread overview]
Message-ID: <1254275160.18930.2.camel@centar> (raw)
In-Reply-To: <4AC283C0.5020704@xunil.at>
On Wed, 2009-09-30 at 00:01 +0200, Stefan G. Weichinger wrote:
> Without any ranting ... I feel kind of stupid waiting for GNOME 2.26
> going stable within the gentoo-tree while GNOME 2.28 is out now at
> gnome.org.
>
> Maybe I am too conservative here and could already use 2.26 for a while
> by unmasking lots of packages or doing *something* ...
>
> Not that I really miss something, it's just that I wonder ... and I
> would like to explore any new features etc ...
>
> The question:
>
> Should I wait for bug 263083 to be done?
>
> https://bugs.gentoo.org/show_bug.cgi?id=263083
>
> Or is there a "safe enough, stable enough" way to get gnome-2.26 onto my
> amd64-desktop without crashing my main workstation every few days?
I haven't found any problems with and I've been running it since it's
been in the tree. I think most of the problems are banged out when it's
in the overlay so by the time the packages make it to the tree they've
already been tested somewhat.
I've found the easiest way to run a suite of packages marked testing is
to go ahead and put yourself in the testing tree. It's easier to mask
packages than to unmask testing ones (even though there are tools now
that supposedly help with that) and testing really isn't that unstable.
If/when there are problems (e.g. cups 1.4.1) the workaround is easy:
report a bug if applicable, mask the offending package and downgrade to
the last version that worked. So come on in. The water's warm :)
-a
next prev parent reply other threads:[~2009-09-30 2:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 22:01 [gentoo-user] gnome 2.26 stable? Stefan G. Weichinger
2009-09-30 1:19 ` [gentoo-user] " walt
2009-09-30 12:43 ` Daniel Troeder
2009-09-30 12:49 ` Stefan G. Weichinger
2009-09-30 13:16 ` Daniel Troeder
2009-09-30 15:56 ` Stefan G. Weichinger
2009-09-30 17:15 ` Stefan G. Weichinger
2009-09-30 19:10 ` Daniel Troeder
2009-10-01 4:48 ` Stefan G. Weichinger
2009-10-01 9:00 ` Daniel Troeder
2009-10-01 13:08 ` Stefan G. Weichinger
2009-10-01 20:15 ` Daniel Troeder
2009-10-02 6:41 ` Stefan G. Weichinger
2009-10-08 7:53 ` Stefan G. Weichinger
2009-09-30 1:46 ` Albert Hopkins [this message]
2009-09-30 2:50 ` [gentoo-user] " Keith Dart
2009-09-30 8:39 ` Stefan G. Weichinger
2009-09-30 13:38 ` Justin
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=1254275160.18930.2.camel@centar \
--to=marduk@letterboxes.org \
--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