From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev-return-5562-arch-gentoo-dev=gentoo.org@gentoo.org>
Received: (qmail 18968 invoked by uid 1002); 13 Aug 2003 22:57:59 -0000
Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Help: <mailto:gentoo-dev-help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Received: (qmail 21593 invoked from network); 13 Aug 2003 22:57:59 -0000
From: Heinrich Wendel <lanius@gentoo.org>
Organization: gentoo
To: Spider <spider@gentoo.org>,
 gentoo-dev@gentoo.org
Date: Thu, 14 Aug 2003 00:57:55 +0200
User-Agent: KMail/1.5.1
References: <200308131844.24013.lanius@gentoo.org> <20030813151404.497059E0.fava@gentoo.org> <20030814005451.1fae2d7e.spider@gentoo.org>
In-Reply-To: <20030814005451.1fae2d7e.spider@gentoo.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200308140057.55368.lanius@gentoo.org>
Subject: Re: [gentoo-dev] Gentoo Menu - Bash vs. Python Rule files
X-Archives-Salt: 879c78c0-a041-4564-9bb4-a437cccd6aef
X-Archives-Hash: c7409cb882a05eb074ad5f9c8e2e64cd

On Thursday 14 August 2003 00:54, Spider wrote:
> 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?
>

That how it works.

Additionally there is a .menu file (which the user can customize) describing 
how to arrange the submenus (take a look at gentoo.menu in cvs).

The only complex thing is that every ebuild that want to support it needs to 
be changed.

> //Spider
mfg, Heinrich :)

--
gentoo-dev@gentoo.org mailing list