From: Tom Philbrick <tom@wickidpisa.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Automatic menus?
Date: Fri, 26 Jul 2002 13:53:37 -0400 [thread overview]
Message-ID: <20020726175337.GA8002@wickidpisa.csh.rit.edu> (raw)
In-Reply-To: <20020726144505.195e1dd4.corvusvcorax@gemia.de>
On Fri, Jul 26, 2002 at 02:45:05PM +0200, Corvus Corax wrote:
> Dont want to bother anyone, but the idea of having to rebuild every ebuild existing for menu data seems not very effective.
It would not be very effective, which is why no one, including myself,
has suggested it. The way this would wor is, there is a program called
update-menus that should be called in the ebuild of any program that
installs a menufile. This program reads through /usr/lib/menu/ which
holds all the menufiles that packages have installed, and from these
files it creates a menu for any program that installs a menu-method (a
file describing how to generate a menu for that program). The menufiles
would be added in with the next update to the ebuild (I assume).
Please read the docs for more:
http://www.debian.org/doc/packaging-manuals/menu.html/index.html
next prev parent reply other threads:[~2002-07-26 17:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 15:08 [gentoo-dev] Automatic menus? Tom Philbrick
2002-07-24 15:14 ` Jon Nelson
2002-07-24 22:46 ` Peter Ruskin
2002-07-24 23:21 ` Grant Goodyear
2002-07-26 12:45 ` Corvus Corax
2002-07-26 13:19 ` Paul de Vrieze
2002-07-26 17:53 ` Tom Philbrick [this message]
2002-07-26 18:03 ` Jean-Michel Smith
2002-07-29 17:22 ` Tom Philbrick
2002-07-29 10:05 ` Noah Justin Norris
-- strict thread matches above, loose matches on Subject: below --
2002-07-25 3:11 Thomas Beaudry
2002-07-25 21:15 ` James Gibson
2002-07-25 21:52 ` Jon Nelson
2002-07-26 3:50 ` Felipe Ghellar
2002-07-26 4:47 ` Tom Philbrick
2002-07-26 5:09 ` Felipe Ghellar
2002-07-26 4:23 ` Tom Philbrick
2002-07-26 1:04 Thomas Beaudry
2002-07-26 2:50 ` James Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020726175337.GA8002@wickidpisa.csh.rit.edu \
--to=tom@wickidpisa.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox