From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GTK und GTK2 Use Flag
Date: Tue, 29 Mar 2005 16:29:36 -0600 [thread overview]
Message-ID: <20050329222936.GF29694@exodus> (raw)
In-Reply-To: <1112132150.13737.9.camel@rivendell>
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
On Tue, Mar 29, 2005 at 11:35:50PM +0200, foser wrote:
> On Tue, 2005-03-29 at 19:20 +0200, Markus Nigbur wrote:
> <snip much gtk2 use flag blah and old ideas>
>
> The gtk2 flag is meant to be removed in time, not to be promoted even
> more -than it was ever meant to be- as it is.
>
> Do it right this time this time, don't try to redo it in as much a
> crappy way as it is now. The proposals here are as much time-context
> dependant as the current solution is.
*cough* quicky question then...
What are you going to do when gtk v3 hits? Deprecate gtk v2? Expect
upstream to quickly migrate all projects/code to v3? Cause projects
sure moved off of v1 in a hurry :P
Continuing, when v3 hits, abuse this same interdependent use flag
trickery interdependent, or move to sane versioned use flags?
Personally at this rate I'm expecting xmms to be gtk1 dependant for as
long as gtk-1* compiles, probably right up through when gtk v3 some
day hits :)
If you use the approach I've laid out (yes, not new, I laid it out in
24439) you wouldn't have to dick around with deprecating a version,
nor essentially mandating what version is default. You'd leave the
total control over what versions the user wants to deal with in the
hands of the _users_, and what versions the package supports would
be represented properly/clearly in the IUSE.
So far... I've not really heard a good reason aside from "it's in
place, we'll just deprecate gtk v1 instead of clean it up" for why
this cannot be corrected _now_, or really in the past.
hell, you even have volunteers. :)
~brian
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-29 22:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 10:15 [gentoo-dev] GTK und GTK2 Use Flag Fabian Zeindl
2005-03-29 10:58 ` Stefan Sperling
2005-03-29 11:04 ` Diego "Flameeyes" Pettenò
2005-03-29 11:11 ` Stefan Sperling
2005-03-29 11:24 ` Diego "Flameeyes" Pettenò
2005-03-29 11:35 ` David Morgan
2005-03-29 11:50 ` Brian Harring
2005-03-29 13:09 ` David Morgan
2005-03-29 13:39 ` Brian Harring
2005-03-29 14:19 ` David Morgan
2005-03-29 15:38 ` Stefan Sperling
2005-03-29 17:20 ` Markus Nigbur
2005-03-29 21:35 ` foser
2005-03-29 21:42 ` Ciaran McCreesh
2005-03-30 9:00 ` Paul de Vrieze
2005-03-29 22:29 ` Brian Harring [this message]
2005-03-29 22:46 ` Ciaran McCreesh
2005-03-29 23:09 ` Olivier Crête
2005-03-29 23:13 ` foser
2005-03-29 23:33 ` Brian Harring
2005-03-30 4:32 ` Dulmandakh Sukhbaatar
2005-03-30 8:44 ` Diego "Flameeyes" Pettenò
2005-03-29 11:05 ` Stefan Sperling
2005-03-29 11:11 ` Brian Harring
2005-03-29 20:49 ` Spider
2005-03-29 22:43 ` Brian Harring
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=20050329222936.GF29694@exodus \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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