From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH 0/2] Correctly determine kernel and initrd versions
Date: Mon, 16 Oct 2017 18:58:59 +0300 [thread overview]
Message-ID: <20171016155901.1724-1-asmirnov@ilbers.de> (raw)
Hello all,
in current Isar implementation, multiconfig file contains hardcoded
version for boot files: kernel and initrd. This is used for both:
- Add respective package to multistrap config.
- Copy boot files to deploy directory.
This series drops this hardcoded versions, so now Isar is able to
determine version of boot files during building.
With best regards,
Alex
Alexander Smirnov (2):
meta-isar: Drop hardcoded kernel versions
meta-isar: Rework boot files copying
meta-isar/conf/multiconfig/qemuamd64-jessie.conf | 5 +----
meta-isar/conf/multiconfig/qemuamd64-stretch.conf | 5 +----
meta-isar/conf/multiconfig/qemuarm-jessie.conf | 5 +----
meta-isar/conf/multiconfig/qemuarm-stretch.conf | 5 +----
meta-isar/conf/multiconfig/qemuarm-wheezy.conf | 5 +----
meta-isar/conf/multiconfig/qemui386-jessie.conf | 5 +----
meta-isar/conf/multiconfig/qemui386-stretch.conf | 5 +----
meta-isar/conf/multiconfig/rpi-jessie.conf | 3 ---
meta/classes/ext4-img.bbclass | 8 --------
meta/classes/image.bbclass | 23 ++++++++++++++++++++---
10 files changed, 27 insertions(+), 42 deletions(-)
--
2.9.4
next reply other threads:[~2017-10-16 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 15:58 Alexander Smirnov [this message]
2017-10-16 15:59 ` [PATCH 1/2] meta-isar: Drop hardcoded kernel versions Alexander Smirnov
2017-10-16 15:59 ` [PATCH 2/2] meta-isar: Rework boot files copying Alexander Smirnov
2017-10-16 16:11 ` Henning Schild
2017-10-16 16:30 ` Alexander Smirnov
2017-10-17 16:08 ` Henning Schild
2017-10-17 18:24 ` Alexander Smirnov
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=20171016155901.1724-1-asmirnov@ilbers.de \
--to=asmirnov@ilbers.de \
--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