| 1 |
On Fri, Sep 02, 2005 at 07:58:05AM +0200, Marius Mauch wrote: |
| 2 |
> On 08/26/05 Brian Harring wrote: |
| 3 |
> |
| 4 |
> > On Fri, Aug 26, 2005 at 11:44:44AM -0400, Dan Meltzer wrote: |
| 5 |
> > > Hows the upgrade path RE: end-user useflag changes? Will everyone |
| 6 |
> > > that has gtk in their make.conf die a horrible death if they don't |
| 7 |
> > > see the upgrade notice? when will they see the upgrade notice? |
| 8 |
> > > Would it make sense to leave the gtk flag for a while at least, to |
| 9 |
> > > ease the end user into an upgrade? |
| 10 |
> > Not saying it's a clean idea, but aside from making a lot of noise |
| 11 |
> > about the change over (which should be delayed till that noise has |
| 12 |
> > been made), a base/profile.bashrc trick of substituting gtk in when |
| 13 |
> > gtk1 is detected would work. |
| 14 |
> |
| 15 |
> Hell no. Don't need to add more confusion to the use flag confusion. |
| 16 |
Instead, confuse the hell out of users who don't religiously follow |
| 17 |
-dev/-user/-gwn, and suddenly get bit by the gtk flag losing it's |
| 18 |
meaning? |
| 19 |
|
| 20 |
That said, it won't work anyways; the aliasing has to occur within the |
| 21 |
python side else it'll screw up the depgraph (realized that just a few |
| 22 |
seconds ago) :) |
| 23 |
|
| 24 |
So... back to making a lot of noise, or some python side support for |
| 25 |
aliasing use flags. |
| 26 |
~harring |
Archives