1 |
On Wed, Oct 14, 2009 at 5:08 PM, Samuli Suominen <ssuominen@g.o> wrote: |
2 |
> New dev-libs/glib, x11-libs/gtk+ and possible some other core libraries |
3 |
> should be in tree (package.masked perhaps) so users and developers can |
4 |
> help testing them. The current way they are moved from overlay into |
5 |
> ~arch is forcing them to be tested, where as having them in tree now, |
6 |
> would allow people who *want* to test them to do so. |
7 |
> |
8 |
|
9 |
I'm not aware of any bugs related to new glib/gtk+ breaking packages |
10 |
in recent times. Probably because Mart (leio) does a really good job |
11 |
of combing through the ChangeLogs and making sure that there aren't |
12 |
any regressions. |
13 |
|
14 |
For instance, with gtk+-2.18, there are major changes which break |
15 |
rendering in apps[1], so it won't be brazenly added to tree (likely |
16 |
will get a p.mask like you say). However, glib-2.22 has no such |
17 |
changes, and will be the first thing to get added to tree as ~arch |
18 |
part of GNOME 2.28. |
19 |
|
20 |
1. Client-Side windows (csw) /will/ break apps; there has been |
21 |
extensive testing upstream, but breakage is inevitable. |
22 |
|
23 |
-- |
24 |
~Nirbheek Chauhan |
25 |
|
26 |
Gentoo GNOME+Mozilla Team |