From: Luke-Jr <luke-jr@gentoo.org>
To: Seemant Kulleen <seemant@gentoo.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: split tcltk USE flag to tcl and tk
Date: Sun, 17 Aug 2003 13:48:54 +0000 [thread overview]
Message-ID: <200308171349.05247.luke-jr@gentoo.org> (raw)
In-Reply-To: <20030817010833.12f78a3d.seemant@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Unless there are Tcl-specific features for an app, why depend on it at all? Tk
depends on Tcl, that's fine. Let Tk's dependency pull it in. Why do Tk-based
programs need to be aware of what Tk depends on?
On Sunday 17 August 2003 08:08 am, Seemant Kulleen wrote:
> This has come up before, and I still wish to voice against it. Like I
> said to Mike (vapier/spanky) in a previous post, and what msterret and I
> are working on fixing through the tree is:
>
> tcltk? ( X? ( blah ) )
>
> which is more accurate. By separating them you run into this error
> case:
>
> USE="-tcl tk"
>
> except that tk needs tcl. And once upon a time they actually were
> separate. I put them together because every ebuild that had a tk dep in
> it was doing:
>
> tcl? ( tcl ) tk? ( tk )
>
> which is just silly really.
>
> My 2 cents,
- --
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/P4fMZl/BHdU+lYMRAiReAJ0QXftG0tEcgjNuHNmkDQrhQuShrQCeN8YO
DGkQ8lpQjTYkyPiHsrJuL0g=
=Iy+F
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-17 13:49 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 [this message]
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=200308171349.05247.luke-jr@gentoo.org \
--to=luke-jr@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=seemant@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