From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: split tcltk USE flag to tcl and tk
Date: Sun, 17 Aug 2003 09:01:10 -0700 [thread overview]
Message-ID: <200308170901.11099.george@gentoo.org> (raw)
In-Reply-To: <20030817083228.GC16981@curie-int.orbis-terrarum.net>
On Sunday 17 August 2003 01:32, Robin H. Johnson wrote:
> Two possible solutions for this:
> 1. Have the 'tk' USE flag imply the 'tcl' USE flag. This would cause the
> 'tcl? ( tcl ) tk? ( tk )' example to resolve correctly.
Perhaps then it should be called tcltk ;). Thus looks like just maintaining
tcltk flag and adding plain "tcl" for the cases where tk is not needed or
desired should resolve this..
George
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-17 16:02 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 [this message]
2003-08-17 13:48 ` Luke-Jr
2003-08-17 8:18 ` Tony Clark
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=200308170901.11099.george@gentoo.org \
--to=george@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