public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Felipe Ghellar <fghellar2@yahoo.com.br>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Automatic menus?
Date: Fri, 26 Jul 2002 00:50:31 -0300	[thread overview]
Message-ID: <3D40C707.3080105@yahoo.com.br> (raw)
In-Reply-To: 20020725165243.58ec047d.jnelson@jamponi.net

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii; format=flowed, Size: 2316 bytes --]

I've thought about something in this line, too.

I'd like to propose a way to implement this feature:

1. Include in the ebuilds a new function to generate the appropriate 
menu files (*.desktop files?). Maybe pkg_postinst() could handle this. 
These files could be stored in the /var/db/pkg/<categoy>/<package>/ 
directory, which already exists for installed packages, and maybe inside 
another subdirectory, e.g. 'menus'.

2. Create a new feature in portage, e.g. 'menus', that can be enabled 
via make.conf:
FEATURES="... menus ..."
In the case that this feature is enabled, the menus are automatically 
created when the package is installed. Otherwise, the menu files are 
just left alone in /var/db/pkg/<categoy>/<package>/menus/.

3. Include a tool in gentoolkit to manually create the menus from the 
menu files if someone decides to start using them after having some 
packages installed. Another tool to remove the menus could also be of use.


Just an idea...

[]'s
Felipe.


Jon Nelson wrote:
> I agree, but think that the menu system (assuming that someday
> there is one) will be "activated" by installing menu (or
> gentoo-menu or whatever), and that individual ebuilds will still
> "install" their little 100 byte description files and so on, but
> that nothing will happen unless you install the menu program.
> 
> The way it worked in Debian was like that. Don't want menus?
> Don't install menu. After 9 years of running 'stable' and you
> *suddenly* have a burning need for menus?  install menu. Tada!
> 
> Note that menu (at least in Debian) is also capable of dealing
> with per-user menu entries.
> 
> After looking at the code, it may be worth doing one of the
> following:
> 
> a) taking the code as-is and just packaging it up (this has been
> done, but not committed to CVS)
> b) taking the code and modifying it for Gentoo
> c) learning from the code and re-implementing in Python (avoids
> problems with g++, g++3.x, and so on)
> 
> I'm in favor of (a) or (b) (they are really the same) in the
> short term, and (c) in the long term, but am not passionate
> about any of it, really.
> 


_______________________________________________________________________
Yahoo! PageBuilder
O super editor para criação de sites: é grátis, fácil e rápido.
http://br.geocities.yahoo.com/v/pb.html


  reply	other threads:[~2002-07-26  3:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  3:11 [gentoo-dev] Automatic menus? Thomas Beaudry
2002-07-25 21:15 ` James Gibson
2002-07-25 21:52   ` Jon Nelson
2002-07-26  3:50     ` Felipe Ghellar [this message]
2002-07-26  4:47       ` Tom Philbrick
2002-07-26  5:09         ` Felipe Ghellar
2002-07-26  4:23     ` Tom Philbrick
  -- strict thread matches above, loose matches on Subject: below --
2002-07-26  1:04 Thomas Beaudry
2002-07-26  2:50 ` James Gibson
2002-07-24 15:08 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
2002-07-26 18:03     ` Jean-Michel Smith
2002-07-29 17:22       ` Tom Philbrick
2002-07-29 10:05 ` Noah Justin Norris

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=3D40C707.3080105@yahoo.com.br \
    --to=fghellar2@yahoo.com.br \
    --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