From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [RFC PATCH 1/6] isar-bootstrap-helper: Add option --copyrepo to setup_root_file_system()
Date: Thu, 14 Jun 2018 10:51:42 +0200 [thread overview]
Message-ID: <20180614105142.402aa87a@md1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <20180613135829.3151-2-mosipov@ilbers.de>
Am Wed, 13 Jun 2018 15:58:24 +0200
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
> Add the option of copying isar-apt repo to rootfs instead of mounting
> it.
>
> Signed-off-by: Maxim Osipov <mosipov@ilbers.de>
> ---
> meta/classes/isar-bootstrap-helper.bbclass | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/isar-bootstrap-helper.bbclass
> b/meta/classes/isar-bootstrap-helper.bbclass index 3c10fc7..7a63914
> 100644 --- a/meta/classes/isar-bootstrap-helper.bbclass
> +++ b/meta/classes/isar-bootstrap-helper.bbclass
> @@ -16,10 +16,12 @@ def reverse_bb_array(d, varname):
>
> setup_root_file_system() {
> CLEAN=""
> + COPYREPO=""
Maybe call that COPYISARAPT --copyisarapt. With the reproducable build
feature still to come we might end up copying many "repos" and the name
could become confusing.
Henning
> FSTAB=""
> while true; do
> case "$1" in
> --clean) CLEAN=1 ;;
> + --copyrepo) COPYREPO=1 ;;
> --fstab) FSTAB=$2; shift ;;
> -*) bbfatal "$0: invalid option specified: $1" ;;
> *) break ;;
> @@ -43,7 +45,11 @@ setup_root_file_system() {
> echo "Package: *\nPin: release n=${DEBDISTRONAME}\nPin-Priority:
> 1000" | \ sudo tee "$ROOTFSDIR/etc/apt/preferences.d/isar" >/dev/null
>
> - sudo mount --bind ${DEPLOY_DIR_APT}/${DISTRO} $ROOTFSDIR/isar-apt
> + if [ ${COPYREPO} ]; then
> + sudo cp -Trpfx ${DEPLOY_DIR_APT}/${DISTRO}
> $ROOTFSDIR/isar-apt
> + else
> + sudo mount --bind ${DEPLOY_DIR_APT}/${DISTRO}
> $ROOTFSDIR/isar-apt
> + fi
> sudo mount -t devtmpfs -o mode=0755,nosuid devtmpfs
> $ROOTFSDIR/dev sudo mount -t proc none $ROOTFSDIR/proc
>
next prev parent reply other threads:[~2018-06-14 8:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 13:58 [RFC PATCH 0/6] ISAR SDK root filesystem Maxim Yu. Osipov
2018-06-13 13:58 ` [RFC PATCH 1/6] isar-bootstrap-helper: Add option --copyrepo to setup_root_file_system() Maxim Yu. Osipov
2018-06-14 8:51 ` Henning Schild [this message]
2018-06-13 13:58 ` [RFC PATCH 2/6] isar-debootstrap: split into host and target recipes Maxim Yu. Osipov
2018-06-14 8:59 ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 3/6] sdkchroot: Added recipe-devel to create SDK root filesystem Maxim Yu. Osipov
2018-06-14 9:19 ` Henning Schild
2018-06-14 10:46 ` Maxim Yu. Osipov
2018-06-14 11:07 ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 4/6] meta/class/image: Add do_isar task to trigger SDK rootfs creation Maxim Yu. Osipov
2018-06-14 9:23 ` Henning Schild
2018-06-14 11:49 ` Maxim Yu. Osipov
2018-06-18 9:56 ` Baurzhan Ismagulov
2018-06-13 13:58 ` [RFC PATCH 5/6] scripts: Add helper scripts to mount/umount chroot directory Maxim Yu. Osipov
2018-06-14 9:28 ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 6/6] doc: Add description of ISAR SDK root filesystem creation Maxim Yu. Osipov
2018-06-14 8:48 ` [RFC PATCH 0/6] ISAR SDK root filesystem Henning Schild
2018-06-14 8:51 ` Jan Kiszka
2018-06-14 9:34 ` Henning Schild
2018-06-14 9:46 ` Maxim Yu. Osipov
2018-06-18 7:08 ` Henning Schild
2018-06-19 7:33 ` Maxim Yu. Osipov
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=20180614105142.402aa87a@md1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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