public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tod M Neidt <tod@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Menu System
Date: 17 Apr 2002 23:22:45 -0500	[thread overview]
Message-ID: <1019103767.3696.1264.camel@Q.neidt.net> (raw)
In-Reply-To: <20020417230748.43bb3722.jnelson@jamponi.net>

On Wed, 2002-04-17 at 23:07, Jon Nelson wrote:
Hi!

My post got mangled and was incomplete. I'm appending it whole :)
> 
> 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.

Only if gnome wasn't in the USE.  But that is a good point, if gnome is
added to the USE later. But then a separate stand alone script could be
made to parse /var/db/pkg/  and just merge any menu items not present
that would be with the new USE variable (ok maybe I'm stretching abit :)

> 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.

Except from my experience debians menu system becomes a complete mess. 
Having to drill down through multiple submenus to get to what you want. 
I, personally don't care for that.

The advantage to this implementation, is that the menu item is inserted
into the existing submenus categories.

Regards,

tod

Full previous post (for what its worth):

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.
For example,

src_install() {

	make blah blah install || die
	 
	dodoc blah blah

	domenu

}


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 necessarily working),

if use gnome; then
    if [ -e ${FILESDIR}/${PN}.desktop]; then
	submenu=$( grep Type ${FILESDIR}/${PN}.desktop | \
	sed "s:\(Type=\)\([[:alpha:]]*\).*:\2:" )
	insinto /usr/share/gnome/apps/${submenu}
	doins ${FILESDIR}/${PN}.desktop
    fi
    if [ -e ${FILESDIR}/${PN}-logo.*]; then
	insinto /usr/share/pixmaps
	doins ${FILESDIR}/${PN}-logo.*
    fi
fi

Presumably, someone familar with the other desktop environments menus
could work up a similar section for those. 







  reply	other threads:[~2002-04-18  4:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 15:07 [gentoo-dev] Menu System Mario Andres Yepes C
2002-04-17 15:18 ` Grant Goodyear
2002-04-17 15:19 ` Jano Lukac
2002-04-17 15:16   ` John Dee
2002-04-17 17:23 ` Dan Armak
2002-04-17 18:08   ` Jon Nelson
2002-04-17 18:56     ` Martin Schlemmer
2002-04-17 22:29     ` Mario Andres Yepes C
2002-04-18  3:41       ` Tod M Neidt
2002-04-18  4:07         ` Jon Nelson
2002-04-18  4:22           ` Tod M Neidt [this message]
2002-04-18 16:01             ` Jon Nelson

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=1019103767.3696.1264.camel@Q.neidt.net \
    --to=tod@gentoo.org \
    --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