Hi Colin (nice name), > I looked into what it would take for Debian's groff package to do a full > rebootstrap from its packaged version of gnulib. It seems relatively > straightforward, but it requires including bootstrap and bootstrap.conf > in tarballs so that we know what modules to use.
I'm testing gnulib-tool.py on packages at the moment and stumbled upon this commit in groff. Another option worth considering is using the gnulib-cache.m4 file. It is pretty small for groff, so here it is minus the copyright header and gnulib-tool invocation comment: # Specification in the form of a few gnulib-tool.m4 macro invocations: gl_LOCAL_DIR([gl]) gl_MODULES([ attribute fprintf-posix git-version-gen havelib snprintf stdbool-c99 stdint sys_wait vsnprintf wcwidth ]) gl_AVOID([]) gl_SOURCE_BASE([lib]) gl_M4_BASE([gnulib_m4]) gl_PO_BASE([]) gl_DOC_BASE([doc]) gl_TESTS_BASE([tests]) gl_LIB([libgnu]) gl_MAKEFILE_NAME([gnulib.mk]) gl_AUTOMAKE_SUBDIR gl_MACRO_PREFIX([gl]) gl_PO_DOMAIN([]) gl_WITNESS_C_MACRO([]) I'm not very familiar with Debian packaging, so I am not sure if there is information you need that is missing there. Here is some links to the relevant documentation which might help: https://www.gnu.org/software/gnulib/manual/gnulib.html#Modified-imports https://www.gnu.org/software/gnulib/manual/gnulib.html#VCS-Issues Collin