Il giorno dom, 17/01/2010 alle 12.48 +0000, Daniel P. Berrange ha scritto: > > .. one file for each logically indepdant block of m4 code from > configure.ac > Then, in the configure.ac file we'd just end up with a set of single > line > calls into these files loooking like > >From one point of view I agree, but I know by experience that this tends to make the various part of the code not in sync one with the other, the result being code repeated and other problems like that. One of the things that I always wanted to work on is a central repository of macros to make autoconf more… sane. Half the AC_ARG_* calls in this configure.in should likely be used from a single macro that encompasses both AC_ARG and AC_HELP, sets the default and validates boolean and tri/state choices. [And in general, the default AC_ARG macros are quite braindamaged, IMHO] > -- Diego Elio Pettenò — “Flameeyes” http://blog.flameeyes.eu/ If you found a .asc file in this mail and know not what it is, it's a GnuPG digital signature: http://www.gnupg.org/ -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list