On Thu, Oct 23, 2008 at 2:33 AM, Julien _FrnchFrgg_ RIVAUD <[EMAIL PROTECTED]> wrote: > Thanks ! > > I think this approach is good: we can add an "INCLUDE=" directive in the > menu file; there will still be a .pekwm/debian-menu, right ? (to account for > local progs like installs in Wine that add an element to .menu)
Yes, there is a debian-menu file in both .pekwm and /etc/pekwm. > > Another way of doing (which may be even better, I don't know), is to create > a script that scans .desktop files and generates a menu; then PewWM would be > freedesktop compliant for menus :) I think I'll work on this later, since getting to work with Debian is the first priorities. I will push it upstream however. > > Currently I put my perso menu in .pekwm/perso_menu, and it includes a > filtered version of the automatic .pekwm/menu to get only the inner of the > RootMenu there. I have implemented this. > > Cheers, > > -- > Julien RIVAUD (_FrnchFrgg_) > The only trouble left is that attempts to install the updated package warn the user that a file modified by a script (/etc/pekwm/menu) is going to be overwritten by a conf-file. I'm still working on the best way to handle this, besides adding a NEWS.Debian file (nothing? echo something in the postinst? manually copy the new file in the postinst?) Once that's done I'll push it to my mentor. Cheers, -- Daniel Moerner <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
