[PATCH] Menu Spec - Desktop specific menus

[Frederic Crozat]

Le mardi 26 septembre 2006 à 00:36 -0700, Bastian, Waldo a écrit :
> >On 9/25/06, Frederic Crozat <fcrozat at mandriva.com> wrote:
> >> Not all distributions :)
> >>
> >> For Mandriva Linux 2007.0, we are storing GNOME and KDE specific
> files
> >> in /etc/xdg/gnome (or /etc/xdg/kde ) and are setting XDG_CONFIG_DIRS
> >> accordingly.
> >>
> >> --
> >> Frederic Crozat <fcrozat at mandriva.com>
> >> Mandriva
> >>
> >
> >Doesn't that break user changes? If both files are called
> >applications.menu kmenuedit and alacarte are going to both edit
> >~/.config/menus/applications.menu which could cause problems.
> 
> It also depends on how smart alacarte is in editing applications.menu.
> If it merges the "parent" menu with the tag that we added for that and
> only makes minimal "add/remove" changes, it should be ok either way.

I think, as Waldo, most users won't switch environment that often, so it
is not a big problem. Moreover, for our own menu system, both GNOME and
KDE uses the same "Mandriva" menu.

ATM, alacarte is a little broken to do such tests (hit, hit, bug
http://bugzilla.gnome.org/show_bug.cgi?id=355828 :) but it is supposed
to do merging.

BTW, kmenudit stores its changes into applications-kmenuedit.menu and
requires  <MergeFile>applications-kmenuedit.menu</MergeFile> to be added
at the end of the /etc/xdg/menus/applications.menu

Another possible caveat for menu modification is that merging is done
following node order in menu file : most shipped menu file add
<DefaultMergeDirs/> at the top of the file, causing any possible change
in the shipped menu structure to be impossible using the
applications-merged directory.

Maybe <DefaultMergeDirs/> should be suggested to implementors to be
added at the end of the file ?

-- 
Frederic Crozat <fcrozat at mandriva.com>
Mandriva