On Wed, Oct 14, 2009 at 5:08 PM, Samuli Suominen <ssuominen@g.o> wrote:
> New dev-libs/glib, x11-libs/gtk+ and possible some other core libraries
> should be in tree (package.masked perhaps) so users and developers can
> help testing them. The current way they are moved from overlay into
> ~arch is forcing them to be tested, where as having them in tree now,
> would allow people who *want* to test them to do so.
>

I'm not aware of any bugs related to new glib/gtk+ breaking packages
in recent times. Probably because Mart (leio) does a really good job
of combing through the ChangeLogs and making sure that there aren't
any regressions.

For instance, with gtk+-2.18, there are major changes which break
rendering in apps[1], so it won't be brazenly added to tree (likely
will get a p.mask like you say). However, glib-2.22 has no such
changes, and will be the first thing to get added to tree as ~arch
part of GNOME 2.28.

1. Client-Side windows (csw) /will/ break apps; there has been
extensive testing upstream, but breakage is inevitable.

-- 
~Nirbheek Chauhan

Gentoo GNOME+Mozilla Team