On Feb 16, 2015, at 11:49 AM, Jeremy Huddleston Sequoia <[email protected]> 
wrote:

> On Feb 16, 2015, at 08:27, Peter Dyballa <[email protected]> wrote:
>> 
>> Am 15.02.2015 um 23:54 schrieb Ken Thomases:
>> 
>>> He gave you links to 1.16.99.1_3 and 1.16.99.901_0 to test.
>> 
>> Yes. What is the procedure or algorithm then to perform tests? Is it, as I 
>> imagined, to leave away this or that or another patch file from the build 
>> process or is it something different? Because I already built, installed, 
>> and used these packages. And they both were not working correctly. So it's 
>> obviously not proper to built them as they are. A second, or third, or 
>> fourth time. Something has to be modified, has to be performed differently. 
>> What? Or how?
>> 
>> Another possibility that comes to my mind is to use modified patch files, 
>> freed off the patches applied to them when they were upgraded. 
> 
> No, it's not at all likely to be one of the patches given that the set of 
> patches didn't change between the versions that introduced the problem.
> 
> Please install 1.16.99.1_3 and tell me if it has the problem you are seeing.  
> Then install 1.16.99.901_0 and tell me if it has the problem you are seeing.

Actually, I have to apologize to Peter.  I had thought your links went to 
ready-made builds, but they don't.  So, the question is how do you expect him 
to install those versions.

Are you suggesting, using MacPorts and doing:

sudo port install xorg-server-devel @1.16.99.1_3

?

Regards,
Ken


_______________________________________________
Xquartz-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/xquartz-dev

Reply via email to