1 |
On 11/24/2011 08:57 PM, Samuli Suominen wrote: |
2 |
> we have a new herd called ayatana (i'm currently the only member, but |
3 |
> anyone intrested is free to join) |
4 |
> |
5 |
> it's aimed at maintaining the ubuntu -invented libraries many apps tend |
6 |
> to use thesedays: |
7 |
> |
8 |
> $ grep -r "herd.*ayatana" */*/metadata.xml |
9 |
> dev-libs/libappindicator/metadata.xml: <herd>ayatana</herd> |
10 |
> dev-libs/libdbusmenu/metadata.xml: <herd>ayatana</herd> |
11 |
> dev-libs/libdbusmenu-qt/metadata.xml: <herd>ayatana</herd> |
12 |
> dev-libs/libindicate/metadata.xml: <herd>ayatana</herd> |
13 |
> dev-libs/libindicate-qt/metadata.xml: <herd>ayatana</herd> |
14 |
> dev-libs/libindicator/metadata.xml: <herd>ayatana</herd> |
15 |
> gnome-extra/indicator-applet/metadata.xml: <herd>ayatana</herd> |
16 |
> net-im/indicator-messages/metadata.xml: <herd>ayatana</herd> |
17 |
> x11-misc/notify-osd/metadata.xml: <herd>ayatana</herd> |
18 |
> xfce-extra/xfce4-indicator-plugin/metadata.xml: <herd>ayatana</herd> |
19 |
> |
20 |
> and perhaps x11-misc/glipper |
21 |
> |
22 |
> summary: |
23 |
> |
24 |
> - keep all the libs and apps using them in sync, since upstream changes |
25 |
> API so often, when you bump one library, you have to bump or patch them all |
26 |
> |
27 |
> - ditch gtk+-2.0 and move all libraries to gtk+-3.0, this will likely |
28 |
> mean lastriting indicator-applet and glipper |
29 |
> |
30 |
> - add more of the project into portage after gtk+-3.0 migration is done: |
31 |
> |
32 |
> https://launchpad.net/ayatana |
33 |
> |
34 |
> |
35 |
> |
36 |
> note: i'm going to be superbusy with work up until x-mas so don't expect |
37 |
> much to happen "too soon" |
38 |
> |
39 |
|
40 |
forgot to add the following disclaimer: |
41 |
|
42 |
I don't want this to become an unmaintainable spagetti, so I prefer we |
43 |
keep this as non invasive as possible. So if Ubuntu has patched GTK+ or |
44 |
Qt toolkits with huge patch that upstream's don't want, then we don't |
45 |
want it either. |