1 |
Am Wed, 24 Jul 2002 11:08:06 -0400 |
2 |
schrieb Tom Philbrick <tom@××××××××××.com>: |
3 |
|
4 |
> Searching the mailing list archives, I see that back in April someone |
5 |
> asked about automatic menus. One reply said that it was already being |
6 |
> worked on, while others said the opposite. Is anyone currently working |
7 |
> on an automatic menu system for gentoo, and if so, what is its status? |
8 |
> |
9 |
--- snap |
10 |
|
11 |
|
12 |
Dont want to bother anyone, but the idea of having to rebuild every ebuild existing for menu data seems not very effective. |
13 |
wouldnt it be better to provide this extra-information in /usr/portage/<class>/<program>/files/menu.<version>.inf for example? |
14 |
so the menu information can sometimes be added to any existing ebuild (and every new) and is read out by any menu application gentoo may provide. maybe write a tool, which regularly updates the used menu-files on installed ebuilds in /var/db/pkg, or make menu systems do this on their own. |
15 |
|
16 |
of course there are many other working methods of doing this, this just an idea. i unfortunately even dont have time to do this myself, but this is a dev-mlist isnt it? <g> |
17 |
|
18 |
what about a tool, which creates menu information for every known menu-system , KDE, Gnome, debian, ..., ... out of this data (/usr/portage/<class>/<program>/files/menu.<version>.inf) at a regular timebase? |
19 |
this should be added to portage itself to be run every time one runs "emerge <item> [unmerge]" :-) |
20 |
|
21 |
just an idea |
22 |
greetings |
23 |
|
24 |
Corvus Corax |