public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 0/5] Debootstrap integration
Date: Thu, 22 Feb 2018 11:20:37 +0300	[thread overview]
Message-ID: <f59dd677-3d84-de86-0823-a8c4991abc5d@ilbers.de> (raw)
In-Reply-To: <20180221115003.11163-1-claudius.heine.ext@siemens.com>

> this patchset contains the change from multistrap to debootstrap.
> 
> 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
>    - 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
> 

Please rebase it on current next. I can't apply this series so can't 
test it. 'next' branch was updated the day before your contribution.

@all: please always rebase your contributions on the latest next. I will 
not apply anything until I'm able to apply and test.

Alex

  parent reply	other threads:[~2018-02-22  8:20 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 ` [PATCH 0/5] Debootstrap integration Jan Kiszka
2018-02-21 21:38   ` Claudius Heine
2018-02-22  8:20 ` Alexander Smirnov [this message]
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=f59dd677-3d84-de86-0823-a8c4991abc5d@ilbers.de \
    --to=asmirnov@ilbers.de \
    --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