public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: foser <foser@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GTK und GTK2 Use Flag
Date: Wed, 30 Mar 2005 01:13:12 +0200	[thread overview]
Message-ID: <1112137992.13737.21.camel@rivendell> (raw)
In-Reply-To: <20050329222936.GF29694@exodus>

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

On Tue, 2005-03-29 at 16:29 -0600, Brian Harring wrote:
> 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.

I know the proposed system obviously and it's still flawed in that
really doesn't deal with USE flag versioning in a consistent,
predictable way.

> 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.

That is all the reason needed here. I'm no biggie on the current
situation (altough if people actually read the USE flag descriptions it
wouldn't be half the issue), but interchanging to be deprecated
behaviour with something just as bad is a regression. I'll post more on
some changes that I'd like to see implemented for this later.

And the issue never has been about changing a few occurances in the
tree.

- foser

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-29 23:13 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
2005-03-29 22:46                           ` Ciaran McCreesh
2005-03-29 23:09                             ` Olivier Crête
2005-03-29 23:13                           ` foser [this message]
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=1112137992.13737.21.camel@rivendell \
    --to=foser@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