From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>,
"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: Sat, 06 Nov 2021 09:43:05 +0000 [thread overview]
Message-ID: <029d18fa589265e32476c7cc45c9977f7b4bb9aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <d87ff011218f55d97e5aa48ff9b06d216f6d477a.camel@iris-sensing.com>
On Fri, 2021-11-05 at 14:09 +0000, Jasper Orschulko wrote:
> Actually, I don't believe this to be an issue for the following
> reasons:
>
> [...]
>
> 2. When using repo within the yocto build itself (with the repo
> fetcher), the repo binary is only ever called during the do_fetch step,
> which obviously has no issues with any network access.
This is not true. The system may be configured for no network access and is
meant just to be building from MIRRORS/PREMIRRORS (see also BB_NO_NETWORK).
One of the reasons for the fetcher abstraction is to allow us to support
features like that. do_fetch is where network access should happen, if the
system is configured for it.
I guess the question becomes whether the usages of repo when using DL_DIR as a
cache will still touch the network?
Cheers,
Richard
next prev parent reply other threads:[~2021-11-06 9:43 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 [this message]
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
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=029d18fa589265e32476c7cc45c9977f7b4bb9aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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 \
/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.