Re: [PATCH v2 0/5] Debootstrap integration

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2018-02-23 21:35, [ext] Jan Kiszka wrote:
> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb b/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb
> index 0eb26f1..af9f494 100644
> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb
> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb
> @@ -75,6 +75,7 @@ do_bootstrap() {
>                               "${DISTRO_SUITE}" \
>                               "${ROOTFSDIR}" \
>                               "${DISTRO_APT_SOURCE}"
> +    sudo rm -f ${ROOTFSDIR}/etc/apt/sources.list
>  }
>  addtask bootstrap before do_build after do_unpack
>  

OK, this does not work as-is because the other targets do not have the
primary repo in their list files. It would probably make sense to
already migrate all repos into the list and extract the primary one from
it, also killing DISTRO_APT_SOURCE.


Anyway, I've tested the series and made some observations, mostly
positive ones:

- The generated images boot and run like the previous ones. Thumbs up!

- The new installation way is stricter with packages, rejecting those
  that try to overwrite files of others. Multistrap was not doing this,
  and I would consider this a weakness of the old way.

- Development round trip times can be shorter due to the initial single
  bootstrap that gets widely reused for the target image build.

- We no longer set a hostname but leave it up to Debian to generate a
  random one. Maybe worth reintroducing this simple customization via an
  overwritable variable.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux