<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 14-02-17 05:42 PM, Mark Kettenis
wrote:<br>
</div>
<blockquote
cite="mid:201402172242.s1HMgWf2031209@glazunov.sibelius.xs4all.nl"
type="cite">
<pre wrap="">Ugh, please no. Can't we just stick to automake 1.x?</pre>
</blockquote>
<br>
We can't stop people from using whatever comes with their distro.
With automake 2.0, it will break and will submit patches to fix it.<br>
<blockquote
cite="mid:201402172242.s1HMgWf2031209@glazunov.sibelius.xs4all.nl"
type="cite">
<pre wrap="">
>From a practical point of view, some of us import Xorg into other
version control systems that don't properly support symlinks.
</pre>
</blockquote>
<br>
This is interesting. Does the imported X code include Mesa Graphics
Library? It already contains links. Examples:<br>
<blockquote><tt>./mesa/mesa/src/gallium/state_trackers/dri/drm/dri_drawable.c</tt><tt><br>
</tt><tt>./mesa/mesa/src/mesa/drivers/dri/r200/radeon_span.c</tt><tt><br>
</tt></blockquote>
I don't know how the X code is imported in the VCS, it is possible
that you get real files instead of links (the tarball does not
contain links). Can you apply the first patch and see what happens?<br>
<br>
Thanks<br>
<br>
<br>
</body>
</html>