To fully archive a `gitsm://` entry in SRC_URI we need to also capture
the submodules recursively. If shallow mirror tarballs are found, they
must be temporarily extracted so that the submodules can be determined.
Signed-off-by: Paul Barker
---
meta/classes/archiver.bbclass | 31
On Mon, 2020-03-09 at 14:21 +, Paul Barker wrote:
> To fully archive a `gitsm://` entry in SRC_URI we need to also capture
> the submodules recursively. If shallow mirror tarballs are found, they
> must be temporarily extracted so that the submodules can be determined.
>
> Signed-off-by: Paul
On Tue, 10 Mar 2020 23:16:38 +
Richard Purdie wrote:
> On Mon, 2020-03-09 at 14:21 +, Paul Barker wrote:
> > To fully archive a `gitsm://` entry in SRC_URI we need to also capture
> > the submodules recursively. If shallow mirror tarballs are found, they
> > must be temporarily extracted
On Wed, 2020-03-11 at 11:31 +, Paul Barker wrote:
> On Tue, 10 Mar 2020 23:16:38 +
> Richard Purdie wrote:
>
> > On Mon, 2020-03-09 at 14:21 +, Paul Barker wrote:
> > > To fully archive a `gitsm://` entry in SRC_URI we need to also capture
> > > the submodules recursively. If shallow
On Wed, 11 Mar 2020 11:38:44 +
Richard Purdie wrote:
> On Wed, 2020-03-11 at 11:31 +, Paul Barker wrote:
> > On Tue, 10 Mar 2020 23:16:38 +
> > Richard Purdie wrote:
> >
> > > On Mon, 2020-03-09 at 14:21 +, Paul Barker wrote:
> > > > To fully archive a `gitsm://` entry in SR
On Wed, 2020-03-11 at 11:50 +, 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
> carri
