On 09/09/2017 09:38 AM, Bruno Haible wrote: > Hello Tim, > >> So if you remove it from bootstrap, I'll update bootstrap in our project >> main >> dir and that's it. > > No, we don't remove it from 'bootstrap'. This piece of backward-compatibility > code is not expensive to keep. > >> @Bruno Maybe it would be wise to just have a symlink to gnulib/build-aux/ >> bootstrap ? > > I don't understand what you mean. Symlinks inside git repositories are a > problem for those people who perform a checkout on Windows.
Another problem is that bootstrap MUST be a shell script rather than a symlink, since one of the purposes of running ./bootstrap is to DO the git submodule checkout. If it is checked into git as a symlink to a submodule, then users have to run something other than ./bootstrap to get the submodule updated, which defeats the purpose of bootstrap being able to do that itself. Yes, that makes bootstrap special as one of the few files that must be copied directly into projects using it, rather than left as a symlink into a submodule. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
