On Sun, 2005-04-24 at 19:15 +0300, nicke wrote: > Follow up on my recent mail. > > I forgot to mention a few things (also, the previous mail became kinda > long)...and I would really like to here some developer comments on my > project. I'm also thinking about setting up a site for this. > > > Things needed still to make this a functioning auto-updated system is > the following: > > * archmenu-fvwm.py to be run after pacman have updated one or several > packages. > > * A config file specifying for which wm/de:s menus should be built. > > * A standard place for menus built from only the system-wise > applications.menu file. So that users can source that if they have no > need to customize things. > > * A way that menus can be built on e per-user basis every time pacman is > run - i.e. user menus that merge the system applications.menu with the > user applications.menu > > > that is it for now > > /nicke
I like that you're basing the conversion off of the .desktop files, which is what we'd planned on doing. On the note of auto-updating systems, every time I've described the functionality, I've said that it won't be auto-updating. The reason is that some users many not want it and we don't want to force it on them. But users that do want easier-to-update menus can run the archmenu* tools at their leisure. Menus will need to be build on a per-user basis, as you said. The way Debian handles their system generated menus is by adding a Debian-> menu to the default. They do that or replace the whole menu. I'm not quite sure who chooses which one it does though. Jason -- If you understand, things are just as they are. If you do not understand, things are just as they are.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
