Simon Josefsson wrote: > I know gnulib never promised to provide code that worked without the > gnulib-tool machinery, but previously the tweaks to make that work > anyway was small. Now they are larger. Before, you'd typically only > have to copy the source code and the M4 files, and arrange for the M4 > macros to be called, and the code would work. I know of some projects > that use gnulib this way (some parts of GnuPG, for example).
Would you mind adding these projects to the 'users' file? From that file, I was under the impression that every gnulib user now uses gnulib-tool. > it seems that > these changes binds source code in gnulib even harder to gnulib-tool. You have a point. I'll back out the change to gnulib-tool. What remains is only the common naming convention of these macros (not _LGPL_PACKAGE here and others there). Instead I'll add an m4 macro GL_MODULE_INDICATOR that does the AC_DEFINE and that can be used in each configure.ac section of a module. Bruno
