1 |
On Friday 26 July 2002 14:45, Corvus Corax wrote: |
2 |
> |
3 |
> Dont want to bother anyone, but the idea of having to rebuild every ebuild |
4 |
> existing for menu data seems not very effective. wouldnt it be better to |
5 |
> provide this extra-information in |
6 |
> /usr/portage/<class>/<program>/files/menu.<version>.inf for example? so the |
7 |
> menu information can sometimes be added to any existing ebuild (and every |
8 |
> new) and is read out by any menu application gentoo may provide. maybe |
9 |
> write a tool, which regularly updates the used menu-files on installed |
10 |
> ebuilds in /var/db/pkg, or make menu systems do this on their own. |
11 |
> |
12 |
I allready saw the problem too, and this might be the answer. |
13 |
> |
14 |
> what about a tool, which creates menu information for every known |
15 |
> menu-system , KDE, Gnome, debian, ..., ... out of this data |
16 |
> (/usr/portage/<class>/<program>/files/menu.<version>.inf) at a regular |
17 |
> timebase? this should be added to portage itself to be run every time one |
18 |
> runs "emerge <item> [unmerge]" :-) |
19 |
|
20 |
Such a tool is what automatic menus is about. The question is how |
21 |
gentoo-specific it will be. I'd like to add to this that I would like the |
22 |
possibility to rearange menu items as I see fit, but still have links removed |
23 |
when I remove software. |
24 |
|
25 |
Paul |
26 |
|
27 |
ps. maybe that feature could be accomplished by using a configuration file |
28 |
that describes "relocations" |
29 |
|
30 |
-- |
31 |
Paul de Vrieze |
32 |
Junior Researcher |
33 |
Mail: pauldv@××××××.nl |
34 |
Homepage: http://www.devrieze.net |