Re: [Qemu-devel] [PATCH v5 00/12] Convert over to use keycodemapdb

["Daniel P. Berrange" <berrange@redhat.com>]

On Tue, Sep 12, 2017 at 03:46:34PM +0200, Gerd Hoffmann wrote:
>   Hi,
> 
> > The keycodemapdb code is designed to be used as a git sub-module, it
> > is
> > not an external dependancy you need installed before use. In this
> > version,
> > however, the sub-module is not directly use. Instead all the
> > generated
> > files are checked into GIT. The downside to this is that we get an
> > enourmous pile of errors from checkpatch.pl. The tool that generates
> > the
> > mapping files doesn't care about QEMU's coding style rules, because
> > it is
> > a general purpose tool intended for use by many different projects.
> > 
> > As such I'm not very happy about the idea of checking the generated
> > files into
> > GIT, and would prefer to go back to generating the files from the
> > submodule
> > on every build, as was done in v4.
> 
> The submodule approach has its share of issues too, just see how many
> patch versions you've needed until patchew builds actually worked.  And
> I guess lots of people have qemu build scripts which likewise need
> adjustments.  Handling of release tarballs must be considered too.
> 
> I still think we should not require a checked out keycodemapdb
> submodule.  But maybe it'll work better if we check in a copy of the
> script and database instead of checking in the generated files.

This feels like it all just defeats the point of submodules if you manually
copy stuff out of the submodule, or checkin generated files.

My POV is that we should a) never check generated files into GIT, and
we should use the submodule in such a way that it is indistinguish
from the content of the submodule being part of the main GIT repo.
IOW, when building from git always initialize the submodule, but
its content gets add to tar.gz dist, so people building from dist
don't rely on the submodule.

This is the way most projects deal with submodules - its been tricky
getting that working because QEMU has not used submodules in the
way other projects normally do, so there's no current framework in
the configure/makefiles todo the right thing. IMHO it is beneficial
to fix this so we can avoid pointless copying of files and/or storing
generated sources

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|