Ralf Corsepius <ralf.corsepius@xxxxxxxxx> writes: >> Please don't make this last change in Autoconf. AC_HEADER_STDBOOL in >> Autoconf works well right now for people who do not use gnulib, > Agreed. I am one of these users. > >> and I >> don't think that it's a good idea to mark obsolescent a working Autoconf >> macro to try to "push" people towards using gnulib instead. > Agreed, again. > > For real-world projects, gnulib often is not a viable alternative. Could you explain why? There are several real-world projects that use gnulib, so I'm curious what the perceived reasons against it are. I'm genuinely interested in the answer to the question, it is not just rethoric because I happen to disagree. I can understand if you are building non-free software you would not want to use gnulib due to license reasons, but you could still use autoconf. However, I'm not sure this is the problem you are thinking of or if there is some technical or other reason. /Simon _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
