1 |
On Wed, 2003-08-13 at 19:45, Heinrich Wendel wrote: |
2 |
> > the "generated by parser or ebuild" that is simple enough. The parser |
3 |
> > should *never* create files in the "legacy" locations, but only in the |
4 |
> > location where we designate the Gentoo menu system would go. Any files |
5 |
> > in the legacy locations would be placed by the package/ebuild and should |
6 |
> > not be considered authorative for our menu system, but rather should be |
7 |
> > parsed to *create* our menu system. For example, if I create an ebuild |
8 |
> > that copies a .desktop file to /usr/share/gnome/apps/Internet and call a |
9 |
> > make_gentoo_menu function at the end of my ebuild, then it should parse |
10 |
> > the file and add it appropriately to the Gentoo menu location. In this |
11 |
> > same token, I should be able to manually create a file in |
12 |
> > /usr/share/applications or /usr/share/gnome/apps/Office or |
13 |
> > /usr/share/applnk and then run a script, say update-menu, and it should |
14 |
> > parse all of the legacy locations and add any new files to the Gentoo |
15 |
> > menu system. Essentially, we should create a new menu system that is |
16 |
> > independent of the others, rather than trying to fix the others. It |
17 |
> > would be fairly trivial to patch the window managers to get their |
18 |
> > information from the Gentoo-created menus as opposed to the intensive |
19 |
> > problem of "fixing" every application that even thinks of installing a |
20 |
> > menu item. This is of course my opinion, but I am trying to keep this |
21 |
> > all on -dev so we can get some good feedback from the users, as they're |
22 |
> > the ones really requesting it. |
23 |
> |
24 |
> How can we make a menu for KDE without writing to /usr/kde/3.1/share/applnk or |
25 |
> /usr/share/applnk ??? |
26 |
|
27 |
You don't. Read the part of my comment that I left in this message. |
28 |
Rather than add OUR menu system to /usr/kde/3.1/share/applnk, we should |
29 |
patch KDE/Gnome/*box/etc (actually quite simple) to use |
30 |
/usr/share/gentoo-menu or wherever we decide the Gentoo menu should go. |
31 |
This saves the problem of having to edit every ebuild right now to |
32 |
implement this, allows for a "Gentoo Menu" support which can easily be |
33 |
turned on or off via FEATURES, and gives us a single location for our |
34 |
entire menu structure, rather than duplicating our parsed menus all over |
35 |
the filesystem. After all, if I have Gnome, KDE, WindowMaker, |
36 |
AfterStep, and Fluxbox installed, the current proposal would have to |
37 |
create 5 separate menus and maintain them to keep everything accurate. |
38 |
Under my proposal, it would only have to maintain ONE and all 5 window |
39 |
managers would use it. At this point you can use ANY version of ANY |
40 |
spec we wish to support, and we don't have to wait on anyone else to |
41 |
support it. |
42 |
|
43 |
-- |
44 |
Chris Gianelloni |
45 |
Developer, Gentoo Linux |