From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: tarballs from git
Date: Thu, 5 Nov 2015 06:17:52 -0700 [thread overview]
Message-ID: <563B5700.3050306@mlbassoc.com> (raw)
I use BB_GENERATE_MIRROR_TARBALLS = "1" to generate tarballs
from the various git-based recipes I use. For the most part
this works great and once the tar file is generated, it just
gets reused.
However, just now I rebuilt my kernel which uses such a git
SRC_URI and the tar file was rebuilt even though I can't see
anything that was newly fetched. I had built from the same
recipe yesterday (today I only touched a patch which changed
neither the recipe nor the SRCREV, etc) and the tar file from
last month was used. Looking through the generated tar file,
I can see that the last file updated was last Oct 5, so there
should have been no reason to rebuild the tar file.
Is there some trace (log file, etc) that might tell me why
this happened?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2015-11-05 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 13:17 Gary Thomas [this message]
2015-11-05 13:23 ` tarballs from git Gary Thomas
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=563B5700.3050306@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/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.