-----Original Message-----
From: Jasper Orschulko <redacted>
Sent: den 11 november 2021 13:10
To: richard.purdie@linuxfoundation.org; openembedded-
core@lists.openembedded.org; kweihmann@outlook.com; Peter Kjellerstedt
[off-list ref]; jasper@fancydomain.eu
Cc: martin@mko.dev; Daniel Baumgart <redacted>;
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 Peter,

quoted

However, this means
that only the source for the repo wrapper is available in DL_DIR. So
when the repo wrapper executes it will try to go on the Internet to
fetch the rest of the repo source, which will fail.

just to clearify: Are we talking about installing repo on a target, or
are we talking about the repo fetcher?

The repo fetcher, i.e., when repo is used by bitbake.

When installing repo on the target, we do not call any "repo" command
within the bitbake build process. We just clone the git repo containing
the wrapper script and install the wrapper script into the sysroot. At
that point the bitbake build process is finished and the user ends up
with just the wrapper script on his device. Just as he would when
installing repo from the system repositories on debian, arch, etc.

When using the fetcher, the repo sources are fetched during the initial
do_fetch (this also works with `bitbake --runonly=do_fetch`) and placed
into the DL_DIR (in the .repo folder, next to the sources as described
in the repo manifest). So unless the user changes something fetcher
related in the recipe or deletes his DL_DIR, he can use this build
environment for an offline build.

How can it work? The repo source, which is fetched by the repo wrapper, 
will not be in DL_DIR or handled by bitbake at all. This means the 
repo wrapper will try to contact googlesource.com directly and fetch it 
when it is run by bitbake, which cannot work since the host is 
disconnected from the network. How or from where would it be able to 
get the sources it needs?

You can try this for yourself, if you like:

1) clone https://github.com/Jasper-Ben/demo-kas
2) (with docker and docker-compose installed) run `make offline-build`

- --
With best regards

Jasper Orschulko
DevOps Engineer

Tel. +49 30 58 58 14 265
Fax +49 30 58 58 14 999
Jasper.Orschulko@iris-sensing.com

• • • • • • • • • • • • • • • • • • • • • • • • • •

iris-GmbH
infrared & intelligent sensors
Schnellerstraße 1-5 | 12439 Berlin

https://iris-sensing.com/

//Peter