From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can we still opt to shallow clone in git?
Date: Thu, 7 Jun 2018 16:18:10 +0200 [thread overview]
Message-ID: <20180607161810.365544bd@windsurf> (raw)
In-Reply-To: <CABKM0pBVG=JptKYBv-dRfhwAkmKCQm09sqLaG44jUyZhE2gPaw@mail.gmail.com>
Hello,
Please keep the Buildroot mailing list in Cc. Thanks!
On Thu, 7 Jun 2018 22:03:13 +0800, qlb1234 wrote:
> In my use case, using whatever is in a branch is still useful. I don't know
> if you or someone else removed it on purpose or unintentionally. Say if I
> provide a patch that brings back this feature, will you consider accepting
> it?
Using branch names as versions for Git-fetched packages was never
supported. Because:
(1) It breaks the principle of reproducibility: the state of the
source code you will build depends on when you do the build.
(2) It doesn't do what you expect, because Buildroot will cache in
DL_DIR a tarball named <package>-master.tar.gz, and will never
re-fetch from the Git repository. To force it to refetch, you have
to manually remove this cached tarball.
See also the thread at
http://lists.busybox.net/pipermail/buildroot/2018-June/222961.html,
where we have been discussing exactly this topic a few days ago.
I still think there are some useful use cases for this, and that we
should support it somehow, but it's not clear how it should be done yet.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-06-07 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 6:37 [Buildroot] Can we still opt to shallow clone in git? qlb1234
2018-06-07 6:41 ` Thomas Petazzoni
[not found] ` <CABKM0pBVG=JptKYBv-dRfhwAkmKCQm09sqLaG44jUyZhE2gPaw@mail.gmail.com>
2018-06-07 14:18 ` Thomas Petazzoni [this message]
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=20180607161810.365544bd@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox