On 23 February 2010 00:34, Bruno Haible <br...@clisp.org> wrote: > Hello Matěj, > > (how do you pronounce your name? like Matyesh?) This one is quite difficult for English speaking people :-) I have found this one on the web and it is quite accurate: Approx English pronunciation for Matej: M as in "me (M.IY)" ; AA as in "odd (AA.D)" ; T as in "tea (T.IY)" ; EY as in "ate (EY.T)" ; Y as in "yield (Y.IY.L.D)"
>> The script solution you have proposed does the job, but I hate when the >> autogen.sh file has more than, let's say, ten lines. > > Well, the autogen.sh script has more to do if you omit more files from > version control. An autogen.sh script of 100 lines doesn't disturb me > much, if it is straightforward. > >> In fact I am >> particularly happy if the job preceding the execution of the ./configure >> script can be done just with autoreconf -i invocation > > 10 years from now, fetching gnulib might be as easy as this. Until then, > you can help making it easier. > >> If I use the code in an autogen.sh of my project, the person that comes >> to the project after me will have a problem, because he/she will have to >> understand and maintain that code. > > The build infrastructure of a project has a size that is essentially > proportional to the size of the project. It is normal to spend, say, 10% > of your effort on build infrastructure. Or 20% in C projects, due to all > the portability issues that remain even with autoconf and gnulib. You are probably right about that, although most people don't like to hear this :-) I have one question, though. Does gnulib-tool do anything else than just copying .m4 and .c files, and playing with lib/Makefile.am? What I mean - I wouldn't mind commiting gnulib stuff to VCS, but only if I can omit files generated by autoreconf. >From reading the manual, I got the impression that it is strictly the either-or approach, but now I think that I have not understood that properly. If it is not the case, then it is not that bad :-) Thanks, Matej
