Bruno Haible <br...@clisp.org> writes: > James Youngman wrote: >> This conflates two separate issues though: >> 1. Which license the developer chooses to use and their strategy for >> updating it >> 2. The technical process by which the project manages files from >> gnulib (e.g. checking them into the repository for their own project >> versus not doing that) >> >> I think it would be great it exercising a deliberate choice on (1) >> didn't force my hand on (2). > > So, are you in favour of removing the 'fdl' module (and let people use > gnulib-tool --copy-file regardless of their updating strategy), or for > creating modules 'fdl-1.2', 'fdl-1.3' (and let people use gnulib-tool > --import for them)?
A fdl-1.3 module already exists. The question is whether to remove the 'fdl' module from gnulib, and ask maintainers (in NEWS) to instead import a specific fdl version. /Simon
