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>
Subject: Incremental target images
Date: Mon, 27 Aug 2018 08:41:52 +0200	[thread overview]
Message-ID: <a19b3d36-8318-cde6-778b-1af7b78f6ea6@siemens.com> (raw)

Hi all,

I was wondering if / how we could model the increasingly common case of 
building very similar target images more efficiently.

A devel image, e.g., likely consists of almost the same base package set 
as the release image. It may only add further packages and maybe replace 
very few (like customization packages). When building both, we could 
save time - specifically when doing cross - by bootstrapping the 
baseline only once. We already do that for the debootstrap step, but not 
yet for further packages.

What do you think? And how could that be modeled from user perspective?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

             reply	other threads:[~2018-08-27  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27  6:41 Jan Kiszka [this message]
2018-08-27  7:25 ` Claudius Heine
2018-08-27  7:44   ` Claudius Heine
2018-08-27  8:29     ` Jan Kiszka
2018-08-27  8:52       ` Claudius Heine
2018-08-27 13:48       ` chombourger

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=a19b3d36-8318-cde6-778b-1af7b78f6ea6@siemens.com \
    --to=jan.kiszka@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