~/.menu
directory.
The files can have an arbitrary file name as long as the new syntax
for the menu entries is used. They should start with either
?package(installed-package):or
?package(local.mystuff):if it's something that isn't ``debian-officially'' installed. (Any ``package'' that starts with ``
local.
'' is considered installed.)
If you are using the old format, the menu entry files should have
names of installed packages or have to be called
``local.name
''. (Note, that due to a bug in menu-1.3
this
did not work then.)
Files including entries with the old syntax either have to use names
of installed packages or have to be named local.name
, since
update-menus assumes any "package" who's name starts
with "local" is installed.
If a user wants to have his/her own menu methods, he/she should create
a ~/.menu-methods
directory and put all scripts he/she wants to
be run in it. (If ~/.menu-methods
exists,
/etc/menu-methods
will not be searched when a user runs
update-menus).
A system admin should place system-wide menu entries in /etc/menu
(not in /usr/lib/menu/package
, since these files will probably
be overwritten by a package upgrade).
/etc/menu
), then this will do the trick:
echo -n > ~/.menu/packageThe zero-size file will tell update-menus that the corresponding package should not have any menu entries listed.