Daniel Moerner a écrit :
severity 503041 serious
tags 503041 pending
thanks
On Tue, Oct 21, 2008 at 6:13 PM, _FrnchFrgg_ <[EMAIL PROTECTED]> wrote:
I'm marking this bug as normal even if there is dataloss (and I can
assure you I lost a fairly complicated and featurefull menu config, as I
assumed that the autogeneration would behave as for pwm).
That's very nice of you, but overwriting local configuration files
violates a must directive of Policy 10.7.3, so this is definitely
severity serious at the least.
This is pending along with 503107. At the moment, the fix I plan to
commit would require you to cp /etc/pekwm/menu ~/.pekwm/menu if you
want to use the new menu generation that splits it out into
/etc/pekwm/menu and /etc/pekwm/debian-menu. This is of course
documented in NEWS.Debian. I will hopefully send this to my sponsor
later tonight and it will ideally filter into Debian soon.
Cheers,
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)
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 :)
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.
Cheers,
--
Julien RIVAUD (_FrnchFrgg_)
