the block would help them see that they cant use 3.x.y unless it is
given a all clear by xorg and ati-drivers teams
ie, dont waste people trying one with the other until it works, those
who can try will anyway and those not capable to step out side the box
will appreciate not fighting xorg 6.8.0-r1 until working ati-drivers
exist, like luke-jr said, dont block a certain version or range, block
Donnie Berkholz wrote:
>On Mon, 2004-10-11 at 15:58, Luke-Jr wrote:
>>On Monday 11 October 2004 9:52 pm, Donnie Berkholz wrote:
>>>On Mon, 2004-10-11 at 15:50, Daniel Goller wrote:
>>>>Guess it is simpler to block on ati-drivers till ati-drivers are fixed.
>>>>But to push 6.8.0-r1 out for anyone to upgrade knowing it will cause
>>>>chaos doesn't seem wise.
>>>How exactly would you like me to do this? I can't block below a specific
>>>version, because I don't know whether the next one released will work. I
>>>can't block all versions, because then they'll never be able to install
>>>one that does work.
>>Any reason you can't block all versions and have the ati-drivers people modify
>>the block to include a specific version once one works?
>Think: Will that help people who have already emerged an ebuild that
>blocks all versions? I'd need a revision bump to change it, which is a
email@example.com mailing list