From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Emilio G. Cota" <cota@braap.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Michal Suchánek" <msuchanek@suse.de>
Subject: Re: [Qemu-devel] Yet another git submodule rant
Date: Fri, 10 Nov 2017 14:22:40 +0000 [thread overview]
Message-ID: <20171110142240.GC30685@redhat.com> (raw)
In-Reply-To: <a1d39dc8-72e1-55a6-7c36-4bbe8b6142fa@ozlabs.ru>
On Sat, Nov 11, 2017 at 12:46:36AM +1100, Alexey Kardashevskiy wrote:
> On 10/11/17 21:41, Daniel P. Berrange wrote:
> > On Fri, Nov 10, 2017 at 09:35:54PM +1100, Alexey Kardashevskiy wrote:
> >> On 09/11/17 00:01, Daniel P. Berrange wrote:
> >>> On Wed, Nov 08, 2017 at 09:26:01AM -0300, Philippe Mathieu-Daudé wrote:
> >>>> On 11/08/2017 06:57 AM, Thomas Huth wrote:
> >>>>>
> >>>>> That automatic git submodule stuff now broke my workflow again. I
> >>>>> usually keep the git repository on my laptop and then simply rsync the
> >>>>> sources (without .git directories) to my target machine to compile it
> >>>>> there. Used to work great for years. Now it's broken, the build process
> >>>>> complains:
> >>>>>
> >>>>> GIT submodule checkout is out of date. Please run
> >>>>> scripts/git-submodule.sh update
> >>>>> from the source directory checkout /home/thuth/devel/qemu
> >>>>>
> >>>>> Running "scripts/git-submodule.sh update" did not fix the issue at all -
> >>>>> I first had to tinker with it for a while to find out that I simply have
> >>>>> to delete ".git-submodule-status" in my git tree to fix the issue.
> >>>>>
> >>>>> I've got the feeling that all this submodule crap is constantly causing
> >>>>> pain ... do we really need this? Can't we find another solution instead?
> >>>>> Or at least stop modifying files automatically in the $SRC_PATH ?
> >>>>
> >>>> Also yesterday on IRC:
> >>>>
> >>>> <RaV3N> [...] I downloaded the qemu source from git and tried to compile
> >>>> it. I am getting this:
> >>>>
> >>>> ./configure --static && make && sudo make install
> >>>> CC ui/input-keymap.o
> >>>> ui/input-keymap.c:8:10: fatal error: ui/input-keymap-linux-to-qcode.c:
> >>>> No such file or directory
> >>>
> >>> I had a pull request merged yesterday later afternoon which possibly
> >>> would address that problem, though hard hard to say for certain.
> >>
> >> wow, already? :(
> >>
> >> I still wonder why do not we checkout submodules into the build directory
> >> and why .git-submodule-status is not there too...
> >
> > That simply isn't the way submodules work, they are inherently part of
> > the source tree, and the status file reflects that too.
>
> Sorry, I am missing the point here. What precisely does prevent us from
> checking out the required modules to the build directory and build them
> there? git provides a submodule repository url and sha1 for the current
> qemu branch.
The build directory should never contain any of your version controlled
source, as that will get irretrievably lost when the build dir is purged.
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 :|
next prev parent reply other threads:[~2017-11-10 14:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 9:57 [Qemu-devel] Yet another git submodule rant Thomas Huth
2017-11-08 10:25 ` Daniel P. Berrange
2017-11-08 12:05 ` Michal Suchánek
2017-11-08 12:34 ` Daniel P. Berrange
2017-11-08 12:43 ` Michal Suchánek
2017-11-08 12:55 ` Daniel P. Berrange
2017-11-08 10:53 ` Gerd Hoffmann
2017-11-08 11:48 ` Thomas Huth
2017-11-08 13:30 ` Philippe Mathieu-Daudé
2017-11-08 16:09 ` Laszlo Ersek
2017-11-08 12:26 ` Philippe Mathieu-Daudé
2017-11-08 13:01 ` Daniel P. Berrange
2017-11-10 10:35 ` Alexey Kardashevskiy
2017-11-10 10:41 ` Daniel P. Berrange
2017-11-10 13:46 ` Alexey Kardashevskiy
2017-11-10 14:01 ` Peter Maydell
2017-11-11 0:15 ` Alexey Kardashevskiy
2017-11-10 14:22 ` Daniel P. Berrange [this message]
2017-11-11 1:10 ` Alexey Kardashevskiy
2017-11-20 1:06 ` Alexey Kardashevskiy
2017-11-09 3:02 ` Alexey Kardashevskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171110142240.GC30685@redhat.com \
--to=berrange@redhat.com \
--cc=aik@ozlabs.ru \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=msuchanek@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.