On Wed, May 01, 2013 at 12:10:33AM -0400, Alexandre Rostovtsev wrote
On Tue, 2013-04-30 at 23:26 -0400, Walter Dnes wrote:
On Tue, Apr 30, 2013 at 11:17:35PM -0400, Alexandre Rostovtsev wrote
It impacts users who use stable keywords and are therefore stuck with
GNOME-2.32. The
On Wed, 2013-05-01 at 04:19 -0400, Walter Dnes wrote:
I think I just realized what this means. I run ICEWM, not GNOME.
GNUMERIC and ABIWORWD and GIMP are the 3 GNOME apps that I use a lot.
Do I have to emerge GNOME-BASE in it's entirety just to get GSettings
working?
Then I misunderstood.
On Wed, May 01, 2013 at 09:22:56AM -0400, Alexandre Rostovtsev wrote
On Wed, 2013-05-01 at 04:19 -0400, Walter Dnes wrote:
I think I just realized what this means. I run ICEWM, not GNOME.
GNUMERIC and ABIWORWD and GIMP are the 3 GNOME apps that I use a lot.
Do I have to emerge GNOME-BASE
On Tue, Apr 30, 2013 at 11:17:35PM -0400, Alexandre Rostovtsev wrote
It impacts users who use stable keywords and are therefore stuck with
GNOME-2.32. The workaround is for affected users to switch to ~arch
keywords (note that GNOME-3.x ebuilds in ~arch get vastly more care and
attention from
It impacts users who use stable keywords and are therefore stuck with
GNOME-2.32. The workaround is for affected users to switch to ~arch
keywords (note that GNOME-3.x ebuilds in ~arch get vastly more care and
attention from us than the theoretically stable GNOME-2.32).
And the real solution
On Tue, 2013-04-30 at 23:26 -0400, Walter Dnes wrote:
On Tue, Apr 30, 2013 at 11:17:35PM -0400, Alexandre Rostovtsev wrote
It impacts users who use stable keywords and are therefore stuck with
GNOME-2.32. The workaround is for affected users to switch to ~arch
keywords (note that
