<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Wed, 2011-06-22 at 10:45 -0700, Dan Nicholson wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#3c3c3c">It's unfortunate that doing this in a backwards compatible way would</FONT></TT><BR>
<TT><FONT COLOR="#3c3c3c">break the argument order convention. It's too bad those didn't just</FONT></TT><BR>
<TT><FONT COLOR="#3c3c3c">get added from the outset. Oh well, it probably won't hurt anything</FONT></TT><BR>
<TT><FONT COLOR="#3c3c3c">significant.</FONT></TT><BR>
</BLOCKQUOTE>
It probably looked overkill at the time :-) Fop is buried under xmlto.<BR>
<BR>
Only libX11 uses XORG_WITH_FOP(no) which will still work as this would be requesting the version number "no" which does not exist. Only if someone used XORG_WITH_FOP(yes) would break. I won't lose sleep over that.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
<TT><FONT COLOR="#3c3c3c">If you want to use the version parameter in any other modules you'll</FONT></TT><BR>
<TT><FONT COLOR="#3c3c3c">have to wait for the util-macros version bump, right?</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
To be safe, yes. Coming soon.<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
</BLOCKQUOTE>
<BR>
I am wondering if for libX11 we should not take this opportunity to use XORG_WITH_FOP([1.0]). This fixes the problem where fop crashes in the nls directory. Few people have 1.0 (not in any Debian distro yet), so it would be equivalent to the current "no". As more people upgrade, it would tell us if there are any other problems. I don't recall if there were other issues. There is some time before next release...
</BODY>
</HTML>