| 1 |
the block would help them see that they cant use 3.x.y unless it is |
| 2 |
given a all clear by xorg and ati-drivers teams |
| 3 |
ie, dont waste people trying one with the other until it works, those |
| 4 |
who can try will anyway and those not capable to step out side the box |
| 5 |
will appreciate not fighting xorg 6.8.0-r1 until working ati-drivers |
| 6 |
exist, like luke-jr said, dont block a certain version or range, block |
| 7 |
it altogether |
| 8 |
|
| 9 |
Donnie Berkholz wrote: |
| 10 |
|
| 11 |
>On Mon, 2004-10-11 at 15:58, Luke-Jr wrote: |
| 12 |
> |
| 13 |
> |
| 14 |
>>On Monday 11 October 2004 9:52 pm, Donnie Berkholz wrote: |
| 15 |
>> |
| 16 |
>> |
| 17 |
>>>On Mon, 2004-10-11 at 15:50, Daniel Goller wrote: |
| 18 |
>>> |
| 19 |
>>> |
| 20 |
>>>>Guess it is simpler to block on ati-drivers till ati-drivers are fixed. |
| 21 |
>>>>But to push 6.8.0-r1 out for anyone to upgrade knowing it will cause |
| 22 |
>>>>chaos doesn't seem wise. |
| 23 |
>>>> |
| 24 |
>>>> |
| 25 |
>>>How exactly would you like me to do this? I can't block below a specific |
| 26 |
>>>version, because I don't know whether the next one released will work. I |
| 27 |
>>>can't block all versions, because then they'll never be able to install |
| 28 |
>>>one that does work. |
| 29 |
>>> |
| 30 |
>>> |
| 31 |
>>Any reason you can't block all versions and have the ati-drivers people modify |
| 32 |
>>the block to include a specific version once one works? |
| 33 |
>> |
| 34 |
>> |
| 35 |
> |
| 36 |
>Think: Will that help people who have already emerged an ebuild that |
| 37 |
>blocks all versions? I'd need a revision bump to change it, which is a |
| 38 |
>complete waste. |
| 39 |
> |
| 40 |
> |
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-dev@g.o mailing list |
Archives