From: Jon Nelson <jnelson@jamponi.net>
To: Tom Philbrick <tom@wickidpisa.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Automatic menus?
Date: Wed, 24 Jul 2002 10:14:57 -0500 [thread overview]
Message-ID: <20020724101457.13c4988c.jnelson@jamponi.net> (raw)
In-Reply-To: <20020724150806.GA5414@wickidpisa.csh.rit.edu>
All I can say is:
You the Man.
It's been on my List of things TO DO.
[I have a very long, getting longer-every-day, list].
Make available what you've got to us, or send it to me,
and I'll make it available, etc...
Thanks, and let's take a look!
On Wed, 24 Jul 2002 11:08:06 -0400
Tom Philbrick <tom@wickidpisa.com> wrote:
> 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?
>
> I ask because I am in the process of porting the debian menu
> system over to gentoo, but I realized I should stop and see if
> it is worth the effort. I have the program working as far as I
> can tell, although I haven't done much testing yet. It still
> needs a lot of work, but most of that is tailoring it to gentoo
> rather than debian (rewriting documentation, and making my
> hacks less of a hack). The build isn't pretty, I see now why
> debian is not a source distro, but it works for now and I'm
> working on cleaning it up.
>
> For those of you that have never used debian (or mandrake, as
> menudrake uses the debian menu system under the hood) you can
> read a good overview of it at:
> http://www.debian.org/doc/packaging-manuals/menu.html/index.html
>
> For the system to work, it would require that every package
> that wants to use a menu must install a menu-method that
> describes how to generate a menu for that program (these can me
> borrowed from debian, or written from scratch). It also would
> require that every application that wanted to be in a menu
> include a simple menu file that describes what the menu entry
> should be. Yes that means a lot of packages would need to be
> updated, but the menufiles take about 30 seconds to write, and
> are simple enough for anyone to do.
>
> So what should I do? Post a new package bug now? Wait until it
> is completely done? Wait until a better time? Give up in favor
> of a more mature, or better, solution?
--
Jon Nelson
Just because it's not broken doesn't mean we can't take it apart.
next prev parent reply other threads:[~2002-07-24 15:14 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 [this message]
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
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=20020724101457.13c4988c.jnelson@jamponi.net \
--to=jnelson@jamponi.net \
--cc=gentoo-dev@gentoo.org \
--cc=tom@wickidpisa.com \
/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