public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Corvus Corax <corvusvcorax@gemia.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Automatic menus?
Date: Fri, 26 Jul 2002 14:45:05 +0200	[thread overview]
Message-ID: <20020726144505.195e1dd4.corvusvcorax@gemia.de> (raw)
In-Reply-To: <20020724150806.GA5414@wickidpisa.csh.rit.edu>

Am Wed, 24 Jul 2002 11:08:06 -0400
schrieb Tom Philbrick <tom@wickidpisa.com>:

> Searching the mailing list archives, I see that back in April someone
> asked about automatic menus. One reply said that it was already being
> worked on, while others said the opposite. Is anyone currently working
> on an automatic menu system for gentoo, and if so, what is its status?
> 
--- snap


Dont want to bother anyone, but the idea of having to rebuild every ebuild existing for menu data seems not very effective.
wouldnt it be better to provide this extra-information in /usr/portage/<class>/<program>/files/menu.<version>.inf for example?
so the menu information can sometimes be added to any existing ebuild (and every new) and is read out by any menu application gentoo may provide. maybe write a tool, which regularly updates the used menu-files on installed ebuilds in /var/db/pkg, or make menu systems do this on their own.

of course there are many other working methods of doing this, this just an idea. i unfortunately even dont have time to do this myself, but this is a dev-mlist isnt it? <g>

what about a tool, which creates menu information for every known menu-system , KDE, Gnome, debian, ..., ... out of this data (/usr/portage/<class>/<program>/files/menu.<version>.inf) at a regular timebase?
this should be added to portage itself to be run every time one runs "emerge <item> [unmerge]" :-)

just an idea
greetings

Corvus Corax


  parent reply	other threads:[~2002-07-26 12:45 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 [this message]
2002-07-26 13:19   ` Paul de Vrieze
2002-07-26 17:53   ` Tom Philbrick
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=20020726144505.195e1dd4.corvusvcorax@gemia.de \
    --to=corvusvcorax@gemia.de \
    --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