On Tue, Apr 18, 2017 at 04:31:16PM +0200, Andrea Bolognani wrote: > This work was motivated by Dan's intention to introduce the > keycodemapdb module into libvirt[1]. As it is, we have a few > useful submodule-related features in our build system, but > they are limited in that they assume there will be a single > submodule, and it will be gnulib. What is it that makes out submodule handling so complicated. eg in gtk-vnc and spice-gtk, we have a trivial line in autogen.sh 'git submodule update --init --recursive' that takes care of it. Is all the complexity we see caused by the need to detect when to re-run bootstrap for gnulib ? Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
