public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ATTENTION!  Broken builds ahead
Date: Sat, 22 Nov 2003 18:43:26 -0500	[thread overview]
Message-ID: <20031122234326.GL17515@time> (raw)
In-Reply-To: <1069544076.26812.16.camel@rivendell>

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

foser wrote:	[Sat Nov 22 2003, 06:34:36PM EST]
> No, it's the same idea the other way around. As mentioned earlier : in
> most cases it was meant as a transition flag. Transition done ? Make the
> stable and maintained UI default. One gtk flag to own them all.

Btw, I would be okay with this (removing the gtk2 flag and switching to
gtk only) except that it would mean the introduction of a local USE-flag
into lots of ebuilds to control whether to build with gtk1 or gtk2 (for
example gvim).  Since I think there would be a few ebuilds in that
position, it makes sense to keep gtk2 as a global flag which is on by
default.

Aron

-- 
Aron Griffis
Gentoo Linux Developer (alpha / ia64 / ruby / vim)
Key fingerprint = E3B6 8734 C2D6 B5E5 AE76  FB3A 26B1 C5E3 2010 4EB0


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

  reply	other threads:[~2003-11-22 23:43 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 [this message]
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

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=20031122234326.GL17515@time \
    --to=agriffis@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