From: Tony Clark <tclark@telia.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: split tcltk USE flag to tcl and tk
Date: Sun, 17 Aug 2003 10:18:39 +0200 [thread overview]
Message-ID: <200308171018.39972.tclark@telia.com> (raw)
In-Reply-To: <20030817075537.GA16981@curie-int.orbis-terrarum.net>
On Sunday 17 August 2003 09.55, Robin H. Johnson wrote:
> I'd like comments on splitting the tcltk USE flag into 'tcl' and 'tk'
> USE flags.
>
> My primary motivation for this is that I am putting together many more
> servers lately, and I need tcl on them, but I don't want X there.
> doing 'USE=tcltk emerge python' pulls in xfree due to
> tcltk? ( ...tk... ) in the python ebuild.
>
> Advantages:
> 1. More accurately reflects what a package uses, and allows for better
> customization.
>
> Disadvantages:
> 2. Changing existing ebuilds to the new style
> 3. Users with tcltk have to update their USE flags.
>
> I am more than willing to bear the brunt of the work of updating the
> ebuilds if there are no objections to this.
Wouldn't it be nicer to use overloading on use flags, so that -X took
priority. ie if -X never build X aware options of any packages.
/tony
--
Contract ASIC and FPGA design.
Telephone +46 702 894 667
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x633E2623
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-08-17 8:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 7:55 [gentoo-dev] RFC: split tcltk USE flag to tcl and tk Robin H. Johnson
2003-08-17 8:02 ` Jon Portnoy
2003-08-17 8:08 ` Seemant Kulleen
2003-08-17 8:32 ` Robin H. Johnson
2003-08-17 13:15 ` Spider
2003-08-18 0:19 ` Georgi Georgiev
2003-09-16 4:06 ` Georgi Georgiev
2003-08-17 16:01 ` George Shapovalov
2003-08-17 13:48 ` Luke-Jr
2003-08-17 8:18 ` Tony Clark [this message]
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=200308171018.39972.tclark@telia.com \
--to=tclark@telia.com \
--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