public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH v5 4/4] doc: added description of `IMAGE_TRANSIENT_PACKAGES`
Date: Tue, 29 May 2018 14:14:25 +0200	[thread overview]
Message-ID: <20180529121425.8783-5-claudius.heine.ext@siemens.com> (raw)
In-Reply-To: <20180529121425.8783-1-claudius.heine.ext@siemens.com>

From: Claudius Heine <ch@denx.de>

---
 doc/user_manual.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index a2f4b92..91f9a6d 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -481,6 +481,22 @@ Isar contains two image type classes that can be used as reference:
 
 ---
 
+## Customize and configure image
+
+Customization and configuration of an image should be done via packages, see below.
+
+Adding those configuration packages to the image can be done in two ways:
+
+ 1. Simply adding the package to `IMAGE_INSTALL`, like any other isar created package, or
+ 2. Adding the package to `IMAGE_TRANSIENT_PACKAGES`.
+
+In most cases adding the configuration package to `IMAGE_INSTALL` is the right option.
+
+In cases were the configuration script of the package has some external dependencies, that should not be part of the final image, then `IMAGE_TRANSIENT_PACKAGES` is the right option.
+Packages in the `IMAGE_TRANSIENT_PACKAGES` variable are installed to the image and purged in the next step. If such a configuration package deploys file as part of their content, then those files will be removed as well.
+
+---
+
 ## Add a Custom Application
 
 Before creating a new recipe it's highly recommended to take a look into the BitBake user manual mentioned in Terms and Definitions section.
-- 
2.17.0


  parent reply	other threads:[~2018-05-29 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 12:14 [PATCH v5 0/4] One-shot configuration packages claudius.heine.ext
2018-05-29 12:14 ` [PATCH v5 1/4] isar-bootstrap|configscript: implement one transient packages claudius.heine.ext
2018-05-29 12:14 ` [PATCH v5 2/4] meta/isar-cfg-localepurge: added locale purge recipe claudius.heine.ext
2018-05-29 12:14 ` [PATCH v5 3/4] meta-isar/isar-image-base: switch use isar-cfg-localepurge claudius.heine.ext
2018-05-29 12:14 ` claudius.heine.ext [this message]
2018-06-01  7:44 ` [PATCH v5 0/4] One-shot configuration packages Maxim Yu. Osipov
2018-06-01  8:13   ` Claudius Heine
2018-06-01  8:43     ` Maxim Yu. Osipov

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=20180529121425.8783-5-claudius.heine.ext@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.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