public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Chao Zeng <chao.zeng@siemens.com>, Le Jin <le.jin@siemens.com>
Subject: [PATCH 4/6] sdk: Do not ship the isar-apt repo
Date: Sun, 22 Mar 2020 09:37:19 +0100	[thread overview]
Message-ID: <e31d8e5fc8acaa206ead2ef11a814b55978eacd7.1584866240.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1584866240.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1584866240.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

Users can add what should be included via SDK_INSTALL now.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/classes/image-sdk-extension.bbclass     | 6 +++---
 meta/recipes-devtools/sdkchroot/sdkchroot.bb | 6 ------
 2 files changed, 3 insertions(+), 9 deletions(-)

diff --git a/meta/classes/image-sdk-extension.bbclass b/meta/classes/image-sdk-extension.bbclass
index 84ac9c6d..6e76b04d 100644
--- a/meta/classes/image-sdk-extension.bbclass
+++ b/meta/classes/image-sdk-extension.bbclass
@@ -8,13 +8,13 @@
 do_populate_sdk[stamp-extra-info] = "${DISTRO}-${MACHINE}"
 do_populate_sdk[depends] = "sdkchroot:do_build"
 do_populate_sdk() {
-    # Copy isar-apt with deployed Isar packages
-    sudo cp -Trpfx ${REPO_ISAR_DIR}/${DISTRO}  ${SDKCHROOT_DIR}/isar-apt
-
     sudo umount -R ${SDKCHROOT_DIR}/dev || true
     sudo umount ${SDKCHROOT_DIR}/proc || true
     sudo umount -R ${SDKCHROOT_DIR}/sys || true
 
+    # Remove isar-apt repo entry
+    sudo rm -f ${SDKCHROOT_DIR}/etc/apt/sources.list.d/isar-apt.list
+
     # Remove setup scripts
     sudo rm -f ${SDKCHROOT_DIR}/chroot-setup.sh ${SDKCHROOT_DIR}/configscript.sh
 
diff --git a/meta/recipes-devtools/sdkchroot/sdkchroot.bb b/meta/recipes-devtools/sdkchroot/sdkchroot.bb
index 2bc9d291..dc765046 100644
--- a/meta/recipes-devtools/sdkchroot/sdkchroot.bb
+++ b/meta/recipes-devtools/sdkchroot/sdkchroot.bb
@@ -49,12 +49,6 @@ SDK_PREINSTALL += " \
 
 S = "${WORKDIR}/rootfs"
 
-ROOTFS_CONFIGURE_COMMAND += "rootfs_configure_isar_apt_dir"
-rootfs_configure_isar_apt_dir() {
-    # Copy isar-apt instead of mounting:
-    sudo cp -Trpfx ${REPO_ISAR_DIR}/${DISTRO} ${ROOTFSDIR}/isar-apt
-}
-
 ROOTFS_POSTPROCESS_COMMAND =+ "sdkchroot_install_files"
 sdkchroot_install_files() {
     # Configure root filesystem
-- 
2.16.4


  parent reply	other threads:[~2020-03-22  8:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22  8:37 [PATCH 0/6] Evolve SDK to chroot-free usage Jan Kiszka
2020-03-22  8:37 ` [PATCH 1/6] sdk: Add support for adding self-defined sdk packages Jan Kiszka
2020-03-22  8:37 ` [PATCH 2/6] sdk: Make all links in the SDK chroot relative Jan Kiszka
2020-03-22  8:37 ` [PATCH 3/6] sdk: Add script to relocate SDK Jan Kiszka
2020-03-22  8:37 ` Jan Kiszka [this message]
2020-03-22  8:37 ` [PATCH 5/6] sdk: Inject sysroot path when calling relocated toolchain Jan Kiszka
2020-03-22  8:55   ` [PATCH v2 " Jan Kiszka
2020-03-22  8:37 ` [PATCH 6/6] sdk: Update README.sdk Jan Kiszka
2020-03-27 23:48 ` [PATCH 0/6] Evolve SDK to chroot-free usage Christopher Larson
2020-03-28  7:33   ` Jan Kiszka

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=e31d8e5fc8acaa206ead2ef11a814b55978eacd7.1584866240.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=chao.zeng@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=le.jin@siemens.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