<!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.26.0"> </HEAD> <BODY> On Wed, 2009-12-09 at 05:27 +0100, Ingmar Vanhassel wrote: <BLOCKQUOTE TYPE=CITE> <PRE> Excerpts from Gaetan Nadon's message of Sun Nov 22 21:59:44 +0100 2009: > Note that xorg-macros.pc is installed in $prefix/share/pkgconfig because > it is architecture independent. I recalled a discussion about libxtrans > that could not cross compile. So will 64e6114 be reverted or not? </PRE> </BLOCKQUOTE> It's more a matter of "when" than "if". The use of the share directory is inevitable in my opinion. However it should be done  in a time sensitive manner. I check a distro which packages macros along other binaries, so it is not expecting them to be in an architecture independent location (unlike other packages). Consider this to be delayed, it will give developers time to adjust. <BLOCKQUOTE TYPE=CITE> <PRE> Any util-macros release in sight? </PRE> </BLOCKQUOTE> The pattern I have seen is that a new version of a package (e.g "Bump to x.y.z") is done prior to a project release. It isn't bumped several times between releases. <BLOCKQUOTE TYPE=CITE> <PRE> Currently util-macros from git is needed to run 'make distcheck' or 'make dist' for a variety of modules. There's also no check in place for a new enough util-macros. </PRE> </BLOCKQUOTE> I think this is the same for all packages, there are no version changes between releases. You should pull all modules from the git master branch. I did a full successful build on all modules yesterday. I also do distcheck often. If it fails and can fix it, I do. Otherwise I ask the maintainer. Let me know if I did not understand your scenario or if you think something is broken. Regards, Gaetan </BODY> </HTML>