Bruce Korb wrote: > > Who will keep it > > up-to-date? The maintainable solution is to use `./posix-modules`. But how? > > Either ... > > b) Invoke ../posix-modules in the bootstrap script of the 'libposix' > > subdirectory. > > Or: > c) create a script that auto-replaces the Depends-on: section of > the module/libposix file? > > Thus, it has the advantage of gnulib-tool magic and it avoids > the maintenance hassle. The bootstrap script *could* just run it. > For that matter, we have a "d": > > d) libposix gets added to modules/.gitignore and libposix/bootstrap > generates it before invoking gnulib-tool ? :-D > > How's "d"?
Yes, why not? You don't even need to fuss with modules/.gitignore. Just remove modules/libposix when you're done. Or create this modules/libposix in a temporary directory: $ mkdir tmp $ mkdir tmp/modules $ func_create_libposix_module > tmp/modules/libposix ... $ gnulib-tool ... --local-dir=tmp ... ... $ rm -rf tmp Bruno
