Bernhard Voelker wrote: > Additionally to updating gnulib, often some projects need to sync additional > files from the freshly updated gnulib subdirectory, like e.g. bootstrap or > COPYING. > ... > WDYT?
Copying files is one thing; that can be done wherever in your build system (autogen.sh, bootstrap, Makefiles), without causing headaches. Doing a 'git pull origin master' from within a Makefile is more hairy. It's OK when none of your co-developer contributes back to gnulib. But when you start to want to make modifications to gnulib and test them using your package, such a mix between version-control stuff and build-related stuff causes major headaches. I know it's tempting: I have such an 'update-gnulib' rule in a Makefile in GNU clisp myself, because it's handy... Bruno
