GNOME Bugzilla – Bug 130340
Using mkinstalldirs in intltoolize add a dep on automake
Last modified: 2004-12-22 21:47:04 UTC
We require automake to be runned before intltoolize but that's not the case for the gnome-common autogen.sh for example.
Raising priority to blocker. Since we exit when we cannot find mkinstalldirs this cause most (or all) build of modules depending on intltool to fail.
so, let's fix gnome-autogen.sh too ? I've ran across this as well, I see no reason not to first run automake
I'm not sure. I'm a bit worried about having such an obscure dependency for people that write their own autogen.sh. Also I have really not have enough auto* knowledge to say for sure this isnt going to cause problems ... CCing Malcom, he seem to have already worked on the XML::Parse and he is gnome-common maintainer. Malcom, the installation of the parser module use mkinstalldirs to create the XML/Parser/Style path. Though mkinstalldirs is created by automake. Currently in gnome-common autogen.sh libtoolize is before automake so we try to run mkinstalldirs but it still does not exist. Any suggestion on how to fix the problem ?
The only alternative is to write a mkinstalldirs equivalent ourselves, which seems dumb. The mkdir features we want are not portable (in particular, -p is the problem). So I would prefer the leave the dependency on automake because it is easier and it lets somebody else maintain mkinstalldirs. I guess another alternative is to flatten the directories that intloolize needs to install (put everything directly under the intltool-modules directory). Then we would only ever have to create one directory (and all mkdir implementations can do that). I thought about doing this originally, but it require subverting the module importing code in OrigTree.pm and possibly (more seriously) in the third-party XML::Parser module as well (it needs to look in another location for its tree implementation).
NOTABUGgging this. I posted 130266 for gnome-common to deal with the dependency.