public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] claudius.heine.ext@siemens.com"
	<claudius.heine.ext@siemens.com>,
	isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 0/5] Debootstrap integration
Date: Wed, 21 Feb 2018 18:37:27 +0100	[thread overview]
Message-ID: <4cd931df-35e1-f0ee-a8c4-89e8b49488c7@siemens.com> (raw)
In-Reply-To: <20180221115003.11163-1-claudius.heine.ext@siemens.com>

On 2018-02-21 12:49, [ext] claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
> 
> Hi,
> 
> this patchset contains the change from multistrap to debootstrap.
> 

Nice!

> There are a view points left on the TODO list, but I think its now at a
> good state to start the discussion about this.
> 
> Here is the TODO list:
> 
> TODO:
>   - Move "DISTRO_APT_SOURCE" and "DISTRO_COMPONENTS" to source list
>     - requires some parsing of the source.list format

Would you consider this todo a blocking point for merging your series
(provided it otherwise works)? The other points below I would see as
things that could be done on top.

Jan

>   - Implement mirror support
>     - requires some parsing of the source.list format as well
>     - propose handling it similar to how PREMIRRORS is done in oe[1]
>   - Implement sharing of apt database:
>     - bind mount local apt index (/var/lib/apt)
>       - ro mount is not possible since it needs to update the isar-apt repo
>         maybe forbid writing to non-local indexies some other way.(ideas?)
>     - bind mount rw local apt package cache (/var/cache/apt)
>       - some care must be taken that no recipe calls 'apt clean' before
>         that is umounted.
> 
> [1] https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-PREMIRRORS
> 
> Cheers,
> Claudius
> 
> Claudius Heine (5):
>   implement isar-bootstrap using debootstrap
>   meta/isar-bootstrap-helper.bbclass: handle rfs customization centrally
>   meta/buildchroot: switch to using isar-bootstrap
>   meta-isar/isar-image-base: switch to using isar-bootstrap
>   meta-isar/multiconfig: remove multistrap references
> 
>  meta-isar/conf/distro/debian-jessie.conf           |   9 +-
>  meta-isar/conf/distro/debian-jessie.list           |   2 +
>  meta-isar/conf/distro/debian-stretch.conf          |   7 +-
>  meta-isar/conf/distro/debian-stretch.list          |   2 +
>  meta-isar/conf/distro/debian-wheezy.conf           |   9 +-
>  meta-isar/conf/distro/debian-wheezy.list           |   2 +
>  meta-isar/conf/distro/raspbian-jessie.conf         |   8 +-
>  meta-isar/conf/multiconfig/qemuarm-jessie.conf     |   2 +-
>  meta-isar/conf/multiconfig/qemuarm-wheezy.conf     |   2 +-
>  meta-isar/conf/multiconfig/rpi-jessie.conf         |   2 +-
>  .../recipes-core/images/files/download_dev-random  |  24 ----
>  .../recipes-core/images/files/multistrap.conf.in   |  38 ------
>  meta-isar/recipes-core/images/files/setup.sh       |  67 -----------
>  meta-isar/recipes-core/images/isar-image-base.bb   |  59 +++-------
>  meta/classes/isar-bootstrap-helper.bbclass         |  36 ++++++
>  meta/recipes-core/isar-bootstrap/isar-bootstrap.bb | 128 +++++++++++++++++++++
>  meta/recipes-devtools/buildchroot/buildchroot.bb   |  54 ++-------
>  meta/recipes-devtools/buildchroot/files/build.sh   |   2 +-
>  .../buildchroot/files/configscript.sh              |  10 --
>  .../buildchroot/files/multistrap.conf.in           |  37 ------
>  meta/recipes-devtools/buildchroot/files/setup.sh   |  72 ------------
>  21 files changed, 214 insertions(+), 358 deletions(-)
>  create mode 100644 meta-isar/conf/distro/debian-jessie.list
>  create mode 100644 meta-isar/conf/distro/debian-stretch.list
>  create mode 100644 meta-isar/conf/distro/debian-wheezy.list
>  delete mode 100644 meta-isar/recipes-core/images/files/download_dev-random
>  delete mode 100644 meta-isar/recipes-core/images/files/multistrap.conf.in
>  delete mode 100755 meta-isar/recipes-core/images/files/setup.sh
>  create mode 100644 meta/classes/isar-bootstrap-helper.bbclass
>  create mode 100644 meta/recipes-core/isar-bootstrap/isar-bootstrap.bb
>  delete mode 100644 meta/recipes-devtools/buildchroot/files/multistrap.conf.in
>  delete mode 100755 meta/recipes-devtools/buildchroot/files/setup.sh
> 

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

  parent reply	other threads:[~2018-02-21 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 11:49 claudius.heine.ext
2018-02-21 11:49 ` [PATCH 1/5] implement isar-bootstrap using debootstrap claudius.heine.ext
2018-02-22  8:11   ` Claudius Heine
2018-02-21 11:50 ` [PATCH 2/5] meta/isar-bootstrap-helper.bbclass: handle rfs customization centrally claudius.heine.ext
2018-02-22  8:20   ` Claudius Heine
2018-02-21 11:50 ` [PATCH 3/5] meta/buildchroot: switch to using isar-bootstrap claudius.heine.ext
2018-02-21 11:50 ` [PATCH 4/5] meta-isar/isar-image-base: " claudius.heine.ext
2018-02-21 11:50 ` [PATCH 5/5] meta-isar/multiconfig: remove multistrap references claudius.heine.ext
2018-02-21 17:37 ` Jan Kiszka [this message]
2018-02-21 21:38   ` [PATCH 0/5] Debootstrap integration Claudius Heine
2018-02-22  8:20 ` Alexander Smirnov
2018-02-22 10:20   ` Claudius Heine

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=4cd931df-35e1-f0ee-a8c4-89e8b49488c7@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ch@denx.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox