From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI, NICE_REPLY_A autolearn=unavailable autolearn_force=no version=4.0.0 Received: from vsmtp.wi.securepipe.com (vsmtp.wi.securepipe.com [64.73.37.228]) by chiba.3jane.net (Postfix) with SMTP id B1A63ACA17 for ; Wed, 17 Apr 2002 23:07:20 -0500 (CDT) Received: (qmail 16486 invoked from network); 18 Apr 2002 03:53:16 -0000 Received: from unknown (HELO honker.jamponi.net) (216.165.183.88) by 0 with SMTP; 18 Apr 2002 03:53:16 -0000 Date: Wed, 17 Apr 2002 23:07:48 -0500 From: Jon Nelson To: gentoo-dev@gentoo.org Cc: tod@gentoo.org Subject: Re: [gentoo-dev] Menu System Message-Id: <20020417230748.43bb3722.jnelson@jamponi.net> In-Reply-To: <1019101288.3695.1250.camel@Q.neidt.net> References: <200204171007.54557.marioy@logos.upb.edu.co> <200204172023.06703.danarmak@gentoo.org> <20020417130833.6250e75b.jnelson@jamponi.net> <200204171729.46831.marioy@logos.upb.edu.co> <1019101288.3695.1250.camel@Q.neidt.net> X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: f22b4ae4-78e5-4fd6-960e-304d20ff7ba4 X-Archives-Hash: 1b241d799319d84d938da99efc656394 On 17 Apr 2002 22:41:27 -0500 Tod M Neidt wrote: > On Wed, 2002-04-17 at 17:29, Mario Andres Yepes C wrote: > > > > I think thats the basic idea... The thing would be that portage should > > provide a couple of functions to easy the process of adding an entry > > to the menu. > > > > Somethink like > > > > add_menu(){ > > mkdir -p ${MENUDIR} > > cat >> ${MENUDIR}/${PN} << EOF > > ?package(${P}): section="$2" icon="$3" title="$4" longtitle="$5" > > needs="$1" command="oo$1" $mimetypes_item > > EOF > > } > > > > So in an ebuild you could have... > > > > add_menu Applications/Games amor.png "A waste of cpu" "Amor, a game" > > x11 > > > > Of course this is just a quick idea, I think that the function could > > be better implemented so the way to call it is more straight forward. > > > > Hi! > > My thought on this issue would be the addition of a 'domenu' helper > script that could be a one line addition in the src_install function. > > The 'domenu' script would cascade through the desktop USE variables > (i.e. gnome, kde, etc , might have to add some for other desktops that > don't already have a USE variable.) If the USE variable for a > particlular desktop is set then insert a menu item. for example (off > the top of my head, so illustrative, not ncessarily working), The problem with that approach is that if you later decide to use gnome, you would have to re-emerge everything to get its menu entry. Having each program place its menu entry (or entries) in a central location (ala Debian, again), and then having a post-process program zip through and create the KDE, GNOME, AfterStep, BlackBox, and so on "system" menus sounds better to me. Porting the "menu" package from Debian shouldn't be hard at all. -- Pound for pound, the amoeba is the most vicious animal on earth. Jon Nelson C and Python Code Gardener