Re: [gentoo-dev] Gentoo Menu - Bash vs. Python Rule files

[Chris Gianelloni <wolf31o2@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 2741 bytes --]

On Wed, 2003-08-13 at 19:45, Heinrich Wendel wrote:
> > the "generated by parser or ebuild" that is simple enough.  The parser
> > should *never* create files in the "legacy" locations, but only in the
> > location where we designate the Gentoo menu system would go.  Any files
> > in the legacy locations would be placed by the package/ebuild and should
> > not be considered authorative for our menu system, but rather should be
> > parsed to *create* our menu system.  For example, if I create an ebuild
> > that copies a .desktop file to /usr/share/gnome/apps/Internet and call a
> > make_gentoo_menu function at the end of my ebuild, then it should parse
> > the file and add it appropriately to the Gentoo menu location.  In this
> > same token, I should be able to manually create a file in
> > /usr/share/applications or /usr/share/gnome/apps/Office or
> > /usr/share/applnk and then run a script, say update-menu, and it should
> > parse all of the legacy locations and add any new files to the Gentoo
> > menu system.  Essentially, we should create a new menu system that is
> > independent of the others, rather than trying to fix the others.  It
> > would be fairly trivial to patch the window managers to get their
> > information from the Gentoo-created menus as opposed to the intensive
> > problem of "fixing" every application that even thinks of installing a
> > menu item.  This is of course my opinion, but I am trying to keep this
> > all on -dev so we can get some good feedback from the users, as they're
> > the ones really requesting it.
> 
> How can we make a menu for KDE without writing to /usr/kde/3.1/share/applnk or 
> /usr/share/applnk ???

You don't.  Read the part of my comment that I left in this message. 
Rather than add OUR menu system to /usr/kde/3.1/share/applnk, we should
patch KDE/Gnome/*box/etc (actually quite simple) to use
/usr/share/gentoo-menu or wherever we decide the Gentoo menu should go. 
This saves the problem of having to edit every ebuild right now to
implement this, allows for a "Gentoo Menu" support which can easily be
turned on or off via FEATURES, and gives us a single location for our
entire menu structure, rather than duplicating our parsed menus all over
the filesystem.  After all, if I have Gnome, KDE, WindowMaker,
AfterStep, and Fluxbox installed, the current proposal would have to
create 5 separate menus and maintain them to keep everything accurate. 
Under my proposal, it would only have to maintain ONE and all 5 window
managers would use it.  At this point you can use ANY version of ANY
spec we wish to support, and we don't have to wait on anyone else to
support it.

-- 
Chris Gianelloni
Developer, Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]