| 1 |
On Fri, Jul 26, 2002 at 02:45:05PM +0200, Corvus Corax wrote: |
| 2 |
> Dont want to bother anyone, but the idea of having to rebuild every ebuild existing for menu data seems not very effective. |
| 3 |
|
| 4 |
It would not be very effective, which is why no one, including myself, |
| 5 |
has suggested it. The way this would wor is, there is a program called |
| 6 |
update-menus that should be called in the ebuild of any program that |
| 7 |
installs a menufile. This program reads through /usr/lib/menu/ which |
| 8 |
holds all the menufiles that packages have installed, and from these |
| 9 |
files it creates a menu for any program that installs a menu-method (a |
| 10 |
file describing how to generate a menu for that program). The menufiles |
| 11 |
would be added in with the next update to the ebuild (I assume). |
| 12 |
Please read the docs for more: |
| 13 |
http://www.debian.org/doc/packaging-manuals/menu.html/index.html |
Archives