Re: [PATCH] technical_overview.md: Update mmdebstrap related bits

[Uladzimir Bely <ubely@ilbers.de>]

On Thu, 2024-11-28 at 16:45 +0530, srinuvasan.a via isar-users wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
> 
> Update technical_overview documentation with mmdebstrap related
> changes.
> 
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
>  doc/technical_overview.md | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/doc/technical_overview.md b/doc/technical_overview.md
> index 0f491c1a..eb19cf52 100644
> --- a/doc/technical_overview.md
> +++ b/doc/technical_overview.md
> @@ -68,7 +68,7 @@ Also called sbuild chroot rootfs, because of the
> usage by sbuild tool.
>  One of the key aspect of Debian philosophy claims the fact, that
> everything in
>  Debian should be built within Debian environment. To follow this
> rule, Isar
>  introduces the new component - schroot rootfs. Schroot rootfs is
> typical Debian
> -filesystem that is created using standard Debian tools: debootstrap,
> apt-get.
> +filesystem that is created using standard Debian tools:
> debootstrap/mmdebstrap, apt-get.
>  The source of packages can be either official Debian repositories or
> custom
>  repositories created by user. It could be one of the following type:
>  
> @@ -80,7 +80,8 @@ repositories created by user. It could be one of
> the following type:
>  Schroot rootfs lifecycle can be described as following:
>  
>   - Schroot rootfs starts out with a minimal base system that was
> generated by
> -   the isar-bootstrap-{host,target} recipe that uses debootstrap and
> apt-get.
> +   the isar-bootstrap-{host,target}/isar-mmdebstrap-{host,target}
> recipe that uses
> +   debootstrap/mmdebstrap respectively and apt-get.
>  
>   - Common development packages needed for packages building are
> installed on
>     top of this rootfs.
> @@ -106,7 +107,7 @@ Target filesystem lifecycle can be described as
> following:
>  
>  Whole Isar build process can be split into the following steps:
>  
> - - Generation of a minimal base system by isar-bootstrap using
> debootstrap and
> + - Generation of a minimal base system by isar-bootstrap/isar-
> mmdebstrap using debootstrap/mmdebstrap and
>     apt for each configuration requested by the user (Debian distro,
> machine and
>     architecture).
>  
> @@ -131,14 +132,14 @@ This recipe implements several tasks which are
> executed in this order:
>  
>  1. `do_generate_keyring`: Generates a new gpg keyring from the gpg
> keys
>     specified in the `APTKEYFILES` variable. This keyring is later
> used by
> -   debootstrap and apt to verify the apt repositories.
> +   debootstrap/mmdebstrap and apt to verify the apt repositories.
>  
>  2. `do_apt_config_prepare`: Generates aggregated apt preferences and
> source
>     files based on the `DISTRO_APT_PREFERENCES` and
> `DISTRO_APT_SOURCES`
>     variables. That are later deployed to the minimal base system to
> be used by
>     `apt` itself.
>  
> -3. `do_bootstrap`: Bootstraps a minimal debian base system using
> debootstrap.
> +3. `do_bootstrap`: Bootstraps a minimal debian base system using
> debootstrap/mmdebstrap.
>  
>  4. `do_apt_config_install`: Installs the apt configuration generated
> by
>     `do_apt_config_prepare` to the base system as well as an apt base
> -- 
> 2.34.1
> 

Applied to next, thanks.

-- 
Best regards,
Uladzimir.



-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/4fe62bdbcd8aed5c06a7e0957dce562cb94c45ae.camel%40ilbers.de.