Josselin Mouette <joss@debian.org> writes: > Le mardi 12 décembre 2006 à 09:17 +0100, Marc 'HE' Brockschmidt a écrit: >> gnome-menu looks OK-ish (though I don't understand the shlibs bump) >> gnome-panel, bug-buddy and eel2 look fine. > The shlibs bump was added to automatically increase the requirement for > these 3 packages on libgnome-menus2. Before the change, they needed to > ask for gnome-applications.menu instead of applications.menu. Now, the > renaming is automatically done within gnome-menus, but if you install > e.g. the new gnome-panel with a pre-2.16.1-1 libgnome-menu2, you'll end > up with an empty menu. Ah, OK. >> I don't understand why only these few packages need to be fixed - what's >> up with other packages (such as alacarte, for example)? > Alacarte does indeed need to be fixed, as it uses > gnome-applications-merged instead of applications-merged. However, > fixing alacarte would require API additions to python-xdg, which doesn't > look reasonable for etch. Will alacarte be useable with the new version of libgnome-menu? I just want to know if anything would break in such a step to partial standard-compliance. Marc -- BOFH #139: UBNC (user brain not connected)
Attachment:
pgpdkaNXpQwZa.pgp
Description: PGP signature