On 07/13/2012 04:40 PM, Eric Blake wrote: >>>> My plan for autoconf is to implement AC_CONFIG_MACRO_DIRS, which can be >>>> invoked multiple times and also takes a whitespace-separated list in a >>>> single call, but which will basically then call AC_CONFIG_MACRO_DIR once >>>> per unique entry (that is, AC_CONFIG_MACRO_DIRS will be smart enough to >>>> filter out duplicates).
Minor setback - existing autoconf already had an internal macro mistakenly named AC_CONFIG_MACRO_DIRS, with the wrong semantics (being internal, it should have been named _AC_CONFIG_MACRO_DIRS, but we can't change the past). While I could rename it, I'm worried that someone using the public documented version in 2.70 but accidentally building with the internal version from 2.69 will have weird errors. I'm thinking we're better off using a slightly different name, so that people accidentally building with older autoconf but using the new macro will get outright failure. Any ideas for the best name to use? Maybe AC_CONFIG_MACRO_DIRS_SECONDARY, since the macro is designed to be use to designate secondary directories where automake will look but not install? AC_CONFIG_OTHER_MACRO_DIRS? >>> I'll keep my automake patches on hold until you have gone ahead with your >>> plan, to avoid introducing inconsistencies and messing up the already >>> suboptimal automake history even more. I suppose you'll also want autoconf 2.70 released so you can actually take advantage of whatever I come up with; and I want to also get the check for a POSIX shell done. Here's hoping I can get to the point of a release in less than a month :) -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
