public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@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 15:15:26 +0200	[thread overview]
Message-ID: <20030817151526.056f2f54.spider@gentoo.org> (raw)
In-Reply-To: <20030817083228.GC16981@curie-int.orbis-terrarum.net>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

begin  quote
On Sun, 17 Aug 2003 01:32:28 -0700
"Robin H. Johnson" <robbat2@gentoo.org> 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.
> 2. the ebuilds doing 'tcl? ( tcl ) tk? ( tk )' are quite clearly
> wrong, as tk is the graphical toolkit for tcl, ergo they should have
> 'IUSE="tk"' and that would pull in tcl as wel


We have that with gtk and gtk2, and users don't understand it. We are at
about 1 bug report / week for that due to the nesting (one turn on/off
and one prefer-gtk2) 

I'd still prefer that the python ebuild was fixed to be:
DEPEND="tcltk? ( X? ( >=dev-lang/tk-8.4 )) " instead of breaking it
further.


//Spider




-- 
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-17 13:15 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 [this message]
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

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=20030817151526.056f2f54.spider@gentoo.org \
    --to=spider@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