Thanks. Ok to install m4/autobuild.m4 too? In acinclude.m4 please.
Accidentally, installing it will fix the problem of having to 'mkdir m4' in order to build inetutils from CVS, which is nice. I think this should be fixed in bootstrap instead. Infact, just issuing `mkdir m4' in bootstrap.conf should work I think; I'll try it and if it works install such a fix. > > Any objections to installing the patch? > > > > My only objection is that m4/ shouldn't be used for this > > macro, the macro should be put in acinclude.m4 instead. > > acinclude.m4 is deprecated according to the Automake manual: > > Oh, I didn't know that. That sucks, and I vehemently disagree with > the stated reasons as well. But on the bright side, it doesn't sound > as if it is deprecated, just discouraged. Do you know if the autoconf > maintainers have any plans on actually removing support for > acinclude.m4? I haven't seen any such plans, but given that many projects still have a acinclude.m4 I doubt it will be soon. Still, I think GNU projects should follow the best-practices set by other GNU projects if feasible. I disagree that splitting it into several small files is `best' practise though. If you have only a few macros as we do, having them in one spot is better than putting some odd 14 files in m4/ for each macro or something equally silly. _______________________________________________ bug-inetutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-inetutils
