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
On 05/01/2013 11:25 AM, Ryan Hill wrote:
Since people like to start whinging threads every time we have to change flags
on gcc this is a friendly notice of some upcoming changes.
[snip lots of good ideas]
Any thoughts?
I'm in favour of unleashing 4.8 in ~arch soon - I've been building
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/30/2013 11:49 PM, Ryan Hill wrote:
On Wed, 01 May 2013 11:33:00 +0800
Patrick Lauer patr...@gentoo.org wrote:
On 05/01/2013 11:25 AM, Ryan Hill wrote:
Since people like to start whinging threads every time we have to change
flags on gcc
