From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Johann Pfefferl <johann.pfefferl@siemens.com>
Subject: [RFC][PATCH] multistrap: Omitting deb-src listings
Date: Thu, 29 Jun 2017 16:47:06 +0200 [thread overview]
Message-ID: <4427685d-f428-7b74-abd9-b1700325d614@siemens.com> (raw)
From: "Dr. Johann Pfefferl" <johann.pfefferl@siemens.com>
Only binary packages are required at the moment.
Signed-off-by: Dr. Johann Pfefferl <johann.pfefferl@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
This seems reasonable also to me. There is just the question if
meta/recipes-devtools/crossbuildchroot/files/multistrap.conf.in should
gain this switch as well.
And I'm wondering if we will need this again when we want to generate an
archive image with the corresponding sources at some point.
meta-isar/recipes-core/images/files/multistrap.conf.in | 1 +
meta/recipes-devtools/buildchroot/files/multistrap.conf.in | 1 +
2 files changed, 2 insertions(+)
diff --git a/meta-isar/recipes-core/images/files/multistrap.conf.in b/meta-isar/recipes-core/images/files/multistrap.conf.in
index 73b6701..50e9898 100644
--- a/meta-isar/recipes-core/images/files/multistrap.conf.in
+++ b/meta-isar/recipes-core/images/files/multistrap.conf.in
@@ -15,3 +15,4 @@ source=##DISTRO_APT_SOURCE##
suite=##DISTRO_SUITE##
components=##DISTRO_COMPONENTS##
packages=##IMAGE_PREINSTALL##
+omitdebsrc=true
diff --git a/meta/recipes-devtools/buildchroot/files/multistrap.conf.in b/meta/recipes-devtools/buildchroot/files/multistrap.conf.in
index 9209fc4..7e88608 100644
--- a/meta/recipes-devtools/buildchroot/files/multistrap.conf.in
+++ b/meta/recipes-devtools/buildchroot/files/multistrap.conf.in
@@ -15,3 +15,4 @@ source=##DISTRO_APT_SOURCE##
suite=##DISTRO_SUITE##
components=##DISTRO_COMPONENTS##
packages=##BUILDCHROOT_PREINSTALL##
+omitdebsrc=true
--
2.12.3
next reply other threads:[~2017-06-29 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 14:47 Jan Kiszka [this message]
2017-06-29 20:49 ` Baurzhan Ismagulov
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=4427685d-f428-7b74-abd9-b1700325d614@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=johann.pfefferl@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