Re: [gentoo-dev] Gnome Stabilization 3.6 or 3.8

[Tom Wijsman <TomWij@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 08 Aug 2013 11:40:58 -0400
Ian Stakenvicius <axs@gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 08/08/13 11:16 AM, Damien Levac wrote:
> > Just a user point of view:
> > 
> > When a user decide to restrict the packages on his system to
> > "stable", I think the user expect stability in the sense works
> > properly under most (if not all) situations.
> 
> That makes a lot of sense, and on that basis keeping gnome-3.8+ in
> ~arch is probably not warranted.  HOWEVER, part of keeping things
> stable is also a stable upgrade path, and -at least at this point- it
> is -not- trivial to go from gnome-2/openrc to gnome-3.8/systemd
> without a fair bit of work on the part of the end-user.

Introducing a new profile [1] to easy the switch in configuration, an
explanation what is being replaced by what, why, and steps to follow;
shouldn't be too hard to follow. When I switched, it wasn't too much.

 [1]: https://bugs.gentoo.org/show_bug.cgi?id=479986
      Please provide a Gnome3 profile enabling "systemd" USE flag

While the bug doesn't mention the other details; this could also include
the other things like disabling the consolekit USE flag, and so on...

> Before anything does go stable, I implore our gnome devs to provide
> cut-and-paste level instructions to do the upgrade, or provide a tool
> to help significantly (if not fully) automate the process.  Our stable
> users should be able to emerge -uDN without spending massive amounts
> of time and who-knows-how-many reboots to resolve the blockages.

+1

> It may be pertinent for this reason (a "smoother" upgrade path) and
> this reason alone, to stabilize gnome-3.6 first -- just to get into
> gnome3 (and get gnome-2 removed) without having to also deal with the
> systemd migration at the same time.

The problem is that GNOME 3.6 is broken for a set of people; which will
cause a lot of unnecessary troubleshooting and bugs, for things that
are already fixed in GNOME 3.8. I'm not convinced that this is smoother.

The concept to not stabilize something you know is more broken applies.

- -- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQEcBAEBAgAGBQJSA74kAAoJEJWyH81tNOV9pAEH/iyo5cOBKSI9X4Xgh3Eor+N+
glBGplKMgDI15KQISHyhCQSeE9HxKLqNdUcHMob4v9dHHAtKCQP8GV9T3ngfeBiK
e2HW/JPD8N6eFfBYnlakKVSI37bhMuTLRgQ8n6WSmhIy8lT/kZtdIo6KNeF4vxIU
FBRxNIUO5fuZJX4gm7gtmBrPWgfnoQi/+N2sgLjuMewKemg+mHLXA7wUPzAN2y2n
RFY+beNG/O8JpP3KZoMysAndzx39WSdgKYWddqPA7xoG+4iy3Msg6Gn+7tOsSFxQ
wcpsoWkDaBXi5arMl3xihcm/1c5Dv75VpUWw09b+r3bkiE5tiiBYi8ryB60iqzo=
=qpn9
-----END PGP SIGNATURE-----