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
signature.asc
Description: This is a digitally signed message part
