System (network) wide menus

Vincent Untz vuntz at
Thu Jan 7 02:11:36 PST 2010


Le mercredi 06 janvier 2010, à 20:01 -1000, Kevin Brammer a écrit :
> From reading through the specifications it seems everything is set up
> for system-wide (machine) options, or per-user options.  What if I want
> menus for all systems on a network, but still want system-independent
> menu options as well as user personal menus?  (My systems - Red Hat Ent.
> 5.x, GNOME)
> Currently, I have XDG_CONFIG_DIRS and XDG_DATA_DIRS pointing at the NFS
> mounted menu directories.  This seems to work for adding my custom menu
> options to the menus, with some exceptions:
> NFS mounted config directories:
> XDG_CONFIG_DIRS=/home/proto/linux/xdg
> XDG_DATA_DIRS=/home/proto/linux/xdg/share
> - If a new user logs in, and attempts to edit a personal menu via
> right-click on the menu bar (alacarte) he's unable to do so because
> alacarte doesn't open.  I'm guessing this is due to the menu files'
> permissions.  (Solution: merge a specific user menu and expect everyone
> to know XML? Add a path to XDG_* variables?)

This sounds like a bug in alacarte. Please launch it from the terminal,
look if there's some output, and file a bug in with
the output.

> - If an exisiting user has edited the menu, and I implement the XDG_*
> variable changes from defaults, he's still able to edit the menus via
> alacarte but no longer sees any updates I make to the menus.

Hrm, this should work since the first thing alacarte does is to create a
user that contains <MergeFile

Again, please file a bug against alacarte, but attach the content of
~/.config/menus/ this time :-)

(on a general note, if you can make sure that the bugs are still valid
with latest versions of alacarte, that'd be great -- I doubt RHEL 5 has
the latest)


Les gens heureux ne sont pas pressés.

More information about the xdg mailing list