| 1 |
On Wed, 2009-09-30 at 00:01 +0200, Stefan G. Weichinger wrote: |
| 2 |
> Without any ranting ... I feel kind of stupid waiting for GNOME 2.26 |
| 3 |
> going stable within the gentoo-tree while GNOME 2.28 is out now at |
| 4 |
> gnome.org. |
| 5 |
> |
| 6 |
> Maybe I am too conservative here and could already use 2.26 for a while |
| 7 |
> by unmasking lots of packages or doing *something* ... |
| 8 |
> |
| 9 |
> Not that I really miss something, it's just that I wonder ... and I |
| 10 |
> would like to explore any new features etc ... |
| 11 |
> |
| 12 |
> The question: |
| 13 |
> |
| 14 |
> Should I wait for bug 263083 to be done? |
| 15 |
> |
| 16 |
> https://bugs.gentoo.org/show_bug.cgi?id=263083 |
| 17 |
> |
| 18 |
> Or is there a "safe enough, stable enough" way to get gnome-2.26 onto my |
| 19 |
> amd64-desktop without crashing my main workstation every few days? |
| 20 |
|
| 21 |
I haven't found any problems with and I've been running it since it's |
| 22 |
been in the tree. I think most of the problems are banged out when it's |
| 23 |
in the overlay so by the time the packages make it to the tree they've |
| 24 |
already been tested somewhat. |
| 25 |
|
| 26 |
I've found the easiest way to run a suite of packages marked testing is |
| 27 |
to go ahead and put yourself in the testing tree. It's easier to mask |
| 28 |
packages than to unmask testing ones (even though there are tools now |
| 29 |
that supposedly help with that) and testing really isn't that unstable. |
| 30 |
If/when there are problems (e.g. cups 1.4.1) the workaround is easy: |
| 31 |
report a bug if applicable, mask the offending package and downgrade to |
| 32 |
the last version that worked. So come on in. The water's warm :) |
| 33 |
|
| 34 |
-a |
Archives