public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: foser <foser@foser.dyn.warande.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ATTENTION!  Broken builds ahead
Date: Sun, 23 Nov 2003 00:31:19 +0100	[thread overview]
Message-ID: <1069543879.26812.11.camel@rivendell> (raw)
In-Reply-To: <200311221746.59542.vapier@gentoo.org>

On Sat, 2003-11-22 at 23:46, Mike Frysinger wrote:
> why not change ?
> as you say, it's always been confusing and it still is confusing ...
> i know every single ebuild i've ever produced/maintained uses the logic 
> gtk==gtk1 and gtk2==gtk2.  i've made a lot of ebuilds ;)
> 
> perhaps it isnt as costly as it may seem to move to a gtk1 and a gtk2 USE flag 
> system ...

It's not confusing to me, it's confusing trough mis- or non-information,
the flag descriptions are sufficiently clear.

I can see why you would want it to change, it's less costly for you ;)

Changing it now would only make it more confusing than it is already.
The intention is to get rid of the flag in time anyway.

- foser


--
gentoo-dev@gentoo.org mailing list


      parent reply	other threads:[~2003-11-22 23:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22  1:17 [gentoo-dev] ATTENTION! Broken builds ahead Spider
2003-11-22  2:18 ` Jason Rhinelander
2003-11-22  2:40   ` Spider
2003-11-22 11:50     ` foser
2003-11-22 22:46       ` Mike Frysinger
2003-11-22 22:57         ` Aron Griffis
2003-11-22 23:06         ` Spider
2003-11-22 23:34           ` foser
2003-11-22 23:43             ` Aron Griffis
2003-11-23  0:05               ` foser
2003-11-22 23:59             ` Spider
2003-11-23 11:21             ` Paul de Vrieze
2003-11-23 11:40               ` Spider
2003-11-23 13:10                 ` foser
2003-11-23 16:43                   ` Paul de Vrieze
2003-11-22 23:31         ` foser [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=1069543879.26812.11.camel@rivendell \
    --to=foser@foser.dyn.warande.net \
    --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