From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"kweihmann@outlook.com" <kweihmann@outlook.com>,
"jasper@fancydomain.eu" <jasper@fancydomain.eu>
Cc: "martin@mko.dev" <martin@mko.dev>,
"Daniel.Baumgart@iris-sensing.net"
<Daniel.Baumgart@iris-sensing.net>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: RE: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
Date: Wed, 10 Nov 2021 23:55:58 +0000 [thread overview]
Message-ID: <dd07e5137044429f805caf23114a2e72@axis.com> (raw)
In-Reply-To: <3101a847508371b09b2949434f9ca09c672a7097.camel@iris-sensing.com>
> -----Original Message-----
> From: bitbake-devel@lists.openembedded.org <bitbake-
> devel@lists.openembedded.org> On Behalf Of Jasper Orschulko
> Sent: den 9 november 2021 12:26
> To: richard.purdie@linuxfoundation.org; openembedded-
> core@lists.openembedded.org; kweihmann@outlook.com; jasper@fancydomain.eu
> Cc: martin@mko.dev; Daniel.Baumgart@iris-sensing.net; bitbake-
> devel@lists.openembedded.org
> Subject: Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe
> for repo 2.17.3
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi Richard,
>
> I think our implementation of the repo fetcher checks the (what I
> believe to be) most relevant parts of your checklist (thanks for the
> write-up). Martin, please corrent me if I'm missing something:
>
> > a) network access for sources is only expected to happen in the
> > do_fetch step.
> > This is not enforced or tested but is required so that we can:
> >
> > i) audit the sources used (i.e. for license/manifest reasons)
> > ii) support offline builds with a suitable cache
> > iii) allow work to continue even with downtime upstream
> > iv) allow for changes upstream in incompatible ways
> > v) allow rebuilding of the software in X years time
>
> check
>
> > b) network access is not expected in do_unpack
>
> check
How do you avoid the repo wrapper fetching the repo source itself
and instead fetch it using the bitbake fetcher? I have seen nothing
to that extent in the patches so far.
//Peter
next prev parent reply other threads:[~2021-11-10 23:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 13:31 [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3 Jasper Orschulko
2021-11-05 13:31 ` [oe-core][PATCH 2/2] base.bbclass: Add sysroot deps for repo fetcher Jasper Orschulko
2021-11-05 13:35 ` [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3 Konrad Weihmann
2021-11-05 13:47 ` Jasper Orschulko
2021-11-05 14:09 ` Jasper Orschulko
2021-11-05 14:20 ` Konrad Weihmann
2021-11-05 14:53 ` Jasper Orschulko
2021-11-05 15:34 ` Jasper Orschulko
2021-11-06 9:43 ` Richard Purdie
2021-11-09 11:26 ` Jasper Orschulko
2021-11-10 12:46 ` Richard Purdie
2021-11-10 13:52 ` Jasper Orschulko
2021-11-10 16:33 ` Richard Purdie
2021-11-11 11:42 ` Jasper Orschulko
2021-11-24 16:04 ` Jasper Orschulko
2021-11-10 23:55 ` Peter Kjellerstedt [this message]
2021-11-11 10:04 ` Jasper Orschulko
2021-11-11 11:34 ` Peter Kjellerstedt
2021-11-11 12:10 ` Jasper Orschulko
2021-11-11 14:11 ` Peter Kjellerstedt
2021-11-11 15:08 ` Jasper Orschulko
2021-11-11 19:20 ` Alexander Kanavin
2021-11-12 12:22 ` Jasper Orschulko
2021-11-15 12:59 ` Jasper Orschulko
2021-11-15 13:05 ` Alexander Kanavin
2021-11-15 13:12 ` Jasper Orschulko
2021-11-05 14:20 ` Alexander Kanavin
2021-11-05 15:04 ` Alexander Kanavin
2021-11-05 15:24 ` Jasper Orschulko
2021-11-05 17:46 ` Alexander Kanavin
2021-11-05 18:05 ` Jasper Orschulko
2021-11-05 18:45 ` Alexander Kanavin
2021-11-05 20:32 ` Jasper Orschulko
2021-11-06 6:39 ` Alexander Kanavin
2021-11-07 9:05 ` Richard Purdie
2021-11-08 11:55 ` Jasper Orschulko
2021-11-08 12:48 ` Fwd: " Richard Purdie
2021-11-09 9:29 ` [docs] " Quentin Schulz
2021-11-09 10:40 ` Fwd: " Michael Opdenacker
2021-11-10 8:47 ` Michael Opdenacker
2021-11-11 10:49 ` Richard Purdie
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=dd07e5137044429f805caf23114a2e72@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=Daniel.Baumgart@iris-sensing.net \
--cc=Jasper.Orschulko@iris-sensing.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jasper@fancydomain.eu \
--cc=kweihmann@outlook.com \
--cc=martin@mko.dev \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.