From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Svyatogor <svyatogor@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Menu - Bash vs. Python Rule files
Date: 14 Aug 2003 07:37:22 -0400 [thread overview]
Message-ID: <1060861042.19245.93.camel@vertigo> (raw)
In-Reply-To: <200308141428.27523.svyatogor@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Thu, 2003-08-14 at 07:28, Svyatogor wrote:
> This is what Debian did and many people complain about this, cause they want
> to be able to use KDE native menu system.
> Answering your question 'Why should I modify every ebuild'. Not every, but
> only the ones which provide some apps with UI. Secondly you don't *have to*.
> If you want users of your app's to edit files themselves - fair enough.
FEATURES=-menu emerge kde
Better yet, the menu FEATURE should NOT be the default, but rather need
to be set by the user to enable the Gentoo menus.
--
Chris Gianelloni
Developer, Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-14 11:33 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 16:44 [gentoo-dev] Gentoo Menu - Bash vs. Python Rule files Heinrich Wendel
2003-08-13 17:19 ` Svyatogor
2003-08-13 17:52 ` Sven Vermeulen
2003-08-13 17:56 ` Spider
2003-08-13 18:32 ` Adam Porich
2003-08-13 19:21 ` Philippe Lafoucrière
2003-08-13 19:19 ` [gentoo-dev] " thomas weidner
2003-08-13 20:38 ` [gentoo-dev] " Chris Gianelloni
2003-08-13 20:38 ` Heinrich Wendel
2003-08-13 21:08 ` Chris Gianelloni
2003-08-13 21:16 ` Heinrich Wendel
2003-08-13 21:50 ` Chris Gianelloni
2003-08-13 21:55 ` Peter Ruskin
2003-08-13 22:17 ` Heinrich Wendel
2003-08-13 23:35 ` Chris Gianelloni
2003-08-14 0:36 ` Heinrich Wendel
2003-08-13 23:48 ` Peter Ruskin
2003-08-14 3:00 ` Mike Frysinger
2003-08-14 8:11 ` [gentoo-dev] Gentoo Menu - Some Comments Svyatogor
2003-08-14 10:02 ` Peter Ruskin
2003-08-14 11:10 ` Chris Gianelloni
2003-08-14 11:31 ` Stuart Herbert
2003-08-14 11:45 ` John
2003-08-14 12:00 ` Chris Gianelloni
2003-08-14 12:01 ` Svyatogor
2003-08-14 15:05 ` Stuart Herbert
2003-08-14 11:34 ` Svyatogor
2003-08-14 11:46 ` Chris Gianelloni
2003-08-14 11:46 ` Paul de Vrieze
2003-08-14 12:02 ` Seemant Kulleen
2003-08-13 22:31 ` [gentoo-dev] Gentoo Menu - Bash vs. Python Rule files Fred Van Andel
2003-08-13 23:09 ` Mike Frysinger
2003-08-13 23:12 ` Heinrich Wendel
2003-08-13 22:14 ` Fred Van Andel
2003-08-13 22:48 ` Heinrich Wendel
2003-08-13 22:54 ` Fred Van Andel
2003-08-14 10:47 ` Chris Gianelloni
2003-08-13 22:54 ` Spider
2003-08-13 22:57 ` Heinrich Wendel
2003-08-14 0:11 ` Spider
2003-08-14 10:49 ` Chris Gianelloni
2003-08-14 10:24 ` Paul de Vrieze
2003-08-14 11:17 ` Chris Gianelloni
2003-08-14 11:22 ` Paul de Vrieze
2003-08-14 11:43 ` Chris Gianelloni
[not found] ` <200308140000.47539.lanius@gentoo.org>
2003-08-13 23:47 ` Chris Gianelloni
2003-08-13 23:45 ` Heinrich Wendel
2003-08-14 0:10 ` Heinrich Wendel
2003-08-14 10:59 ` Chris Gianelloni
2003-08-14 10:56 ` Chris Gianelloni
2003-08-14 11:10 ` Toby Dickenson
2003-08-14 11:19 ` Chris Gianelloni
2003-08-14 11:28 ` Svyatogor
2003-08-14 11:37 ` Chris Gianelloni [this message]
2003-08-14 11:53 ` Paul de Vrieze
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=1060861042.19245.93.camel@vertigo \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=svyatogor@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