From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Henning Schild <henning.schild@siemens.com>,
bitbake-devel@lists.openembedded.org
Cc: isar-users@googlegroups.com
Subject: Re: [bitbake-devel] [PATCH] fetch/git: add support for disabling shared clones on unpack
Date: Tue, 13 Apr 2021 11:23:00 +0100 [thread overview]
Message-ID: <65bf5f7ea9041131d5106cd45cf19e709f468d2d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210412170519.53612c01@md1za8fc.ad001.siemens.net>
Hi,
On Mon, 2021-04-12 at 17:05 +0200, Henning Schild wrote:
> this is still pretty much relevant to Isar, where an unpack with git
> goes into a chroot. Having a way not clone "shared" would really help
> us in Isar.
>
> Any comments? Except for this one maybe not applying anymore, did not
> try.
I'm torn on this, I can see the use case but it isn't one we've typically
run into. I can see how it is Isar specific.
I'm hesitant as the more "forks" in codepath we add to the fetcher, the
harder it becomes to test and maintain.
Would you be able to add some tests for this to the testsuite
(bitbake-selftest)? If we have some tests we could probably add something.
I did also wonder whether this should be a per url parmeter or a global
fetcher behaviour option? You'd end up adding this to all urls in your
usecase?
Cheers,
Richard
next prev parent reply other threads:[~2021-04-14 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 16:42 Henning Schild
2017-12-20 16:44 ` Henning Schild
2017-12-20 16:45 ` Henning Schild
2018-01-30 12:18 ` Henning Schild
2021-04-12 15:05 ` [bitbake-devel] " Henning Schild
2021-04-13 10:23 ` Richard Purdie [this message]
2021-04-13 12:40 ` Henning Schild
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=65bf5f7ea9041131d5106cd45cf19e709f468d2d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox