On 07/24/2018 10:49 PM, Eric Blake wrote:
> As long as any customizations can be characterized into cfg.mk overrides and
> the generic
> rule in maint.mk knows how to honor those overrides, it seems like it should
> work.
> But I'm not sure what data representation would be easiest to manipulate into
> those overrides.
maybe a simple variable?
gnulib_sync_files='\
gnulib/doc/COPYINGv3 COPYING
gnulib/build-aux/bootstrap bootstrap
gnulib/tests/init.sh tests/init.sh
' # Gnulib file # file in project
and then doing a loop over it line-by-line?
> A different approach would be using git symlinks that point into the git
> submodule
> (then your local file is always up-to-date if your submodule is up-to-date).
This has 2 aspects:
a) I'm no lawyer, but I guess the 'COPYING' file needs to be in the
project repository physically, i.e., no symlink.
b) Sometimes, a project may choose not to take a newer version (yet),
or may need to have a local change which didn't make it into upstream
gnulib for whatever reason.
Have a nice day,
Berny
