From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <pbarker@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/5] archiver.bbclass: Handle gitsm URLs in the mirror archiver
Date: Wed, 11 Mar 2020 11:53:04 +0000 [thread overview]
Message-ID: <05d49916fe80df0b5e085113873d678c10270f40.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200311115025.56045856@ub1910>
On Wed, 2020-03-11 at 11:50 +0000, Paul Barker wrote:
> I structured things this way after the discussions we've had previously about
> not wanting to add too many new code paths to the fetcher. I'd also like to
> keep the logic in a bbclass as much as possible so that it can be more easily
> carried as a local backport to earlier Yocto Project releases.
>
> I do see your point though, this is liable to grow warts over time as special
> cases are added for different fetchers.
I appreciate the previous discussions, but yes, this is my concern.
> The cause of the warts here is that the gitsm fetcher downloads and creates
> mirror tarballs for sources which aren't listed in SRC_URI. The archiver
> would be simpler if we could assume that all sources are included in SRC_URI.
> Perhaps the solution is not to add a "make a mirror copy" API but instead add
> an "expand SRC_URI with any dependencies" API that the archiver can call
> before it iterates over the list of sources.
Yes, that sounds like good insight into the real issue and would make
sense, I think that would improve things and alleviate my concerns.
Cheers,
Richard
next prev parent reply other threads:[~2020-03-11 11:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 14:21 [PATCH 0/5] Archiver and externalsrc fixes Paul Barker
2020-03-09 14:21 ` [PATCH 1/5] archiver.bbclass: Handle gitsm URLs in the mirror archiver Paul Barker
2020-03-10 23:16 ` Richard Purdie
2020-03-11 11:31 ` Paul Barker
2020-03-11 11:38 ` Richard Purdie
2020-03-11 11:50 ` Paul Barker
2020-03-11 11:53 ` Richard Purdie [this message]
2020-03-09 14:21 ` [PATCH 2/5] archiver.bbclass: Make do_deploy_archives a recursive dependency Paul Barker
2020-03-10 23:18 ` Richard Purdie
2020-03-11 11:40 ` Paul Barker
2020-04-01 14:49 ` [OE-core] " Mark Hatle
[not found] ` <1601B99892621331.16702@lists.openembedded.org>
2020-04-01 17:20 ` Mark Hatle
2020-03-09 14:21 ` [PATCH 3/5] kernelsrc.bbclass: Fix externalsrc support Paul Barker
2020-03-09 14:21 ` [PATCH 4/5] perf: " Paul Barker
2020-03-09 14:21 ` [PATCH 5/5] kernel-yocto.bbclass: Support config fragments with externalsrc Paul Barker
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=05d49916fe80df0b5e085113873d678c10270f40.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pbarker@konsulko.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