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

[Spider <spider@gentoo.org>]

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

begin  quote
On Wed, 13 Aug 2003 15:14:04 -0700
Fred Van Andel <fava@gentoo.org> wrote:


> So how do I use this in an ebuild.
> 
> Do I have to write customized versions of start_menu() etc for each
> ebuild or do I call the start_menu() etc functions from within
> src_install() or will they be called automatically using on some
> defined variables as parameters?
> 

-as I understood it-,

 each  package that wishes to do so should provide an .desktop file
(which is freedesktop standard, and KDE and Gnome have each implemented
them) and then a rule system (written with one rule-parser for each
system. ie, one for black/open/flux - box, one for WindowMaker, one for
Waimea and so on. KDE and Gnome both have their own builtin and"just do
it" . theese rulemakers will then parse the desktop files(via a common
frontend to read the desktopfiles) and add entries to the menu at
rebuildtime.


A desktop file is basically a list (With translations) of the following
entries:

[Desktop Entry]
Name=Megalomaniac example
Exec=megalomaniac-exp --run
Icon=megalomaniac.png
Type=Application
Categories=Gentoo;Application;Development
---

With as many extra fields included as you wish. Theese all install into
a centralized place and is a standard commodity which can be parsed by
rulesets into the menu for, ex. Fluxbox ..


lanius, Svyatogor, correct me if I'm wrong or oversimplifying things
here?

//Spider

-- 
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]