From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: 'IMAGE_FEATURES' in Isar
Date: Wed, 11 Apr 2018 14:59:38 +0200 [thread overview]
Message-ID: <8cc3abfe-de1b-fb63-b58d-7a73561c11ae@siemens.com> (raw)
Hi,
since we discussed that we might want to implement 'IMAGE_FEATURES' in
Isar in order to support images without kernel, I wanted to start some
brainstorming about what this should be used in other cases.
While discussing that with Jan we came some ideas that would be nice to
be implemented as features:
- Cleanup steps like localepurge, and apt-get clean
- Removal of apt and other possible reduction tasks
- ??? other ideas?
About installing the kernel: It could be possible to have some
'nokernel' feature, but I am currently not sure if that is right.
Debians 'debootstrap' does not install a kernel per default, so if we
now have a kernel per opt-out we are a bit in a conflict with the
'Debian-Way-Of-Life' IMO. Because there even the kernel is a opt-in
package. Of course most images created by Isar will have a kernel, so I
also see that reason for including one.
The other question might be if having a kernel should be implemented as
a IMAGE_FEATURE or rather a setting in the machine.conf? In the simplest
solution maybe something like:
machine.conf:
KERNEL='yes'
while the multiconfig specifies which kernel to use and the distro what
kernels are available, like it does today.
What do you think?
Thanks,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next reply other threads:[~2018-04-11 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 12:59 Claudius Heine [this message]
2018-04-12 14:26 ` Baurzhan Ismagulov
2018-04-12 15:35 ` Claudius Heine
2018-04-13 11:27 ` Baurzhan Ismagulov
2018-04-16 8:17 ` Claudius Heine
2018-04-16 8:36 ` 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=8cc3abfe-de1b-fb63-b58d-7a73561c11ae@siemens.com \
--to=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