From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v4 0/3] One-shot configuration packages
Date: Tue, 29 May 2018 11:29:57 +0200 [thread overview]
Message-ID: <3e88b5b4-53b8-613d-ac35-00f8643fa232@siemens.com> (raw)
In-Reply-To: <20180529080011.GA4816@yssyq.radix50.net>
Hi Baurzhan,
On 2018-05-29 10:00, Baurzhan Ismagulov wrote:
> Hello Claudius,
>
> this is a useful feature that is also user-visible. Would you like to provide a
> patch to doc/user_manual.md?
I will do that and send a v5. But I answer your questions here as well.
For me its easier to explain something in a dialog that just writing
docs to someone unknown. :)
> I think we should provide a recommendation for the
> user how to do customizations. I'd be especially interested in your vision
> where to provide what, e.g.: One or many customization packages?
Currently I cannot think of anything else that could be done with those
one-shot packages apart from localepurge. Is generally only useful if
someone needs a tool to customize the root file system that shouldn't be
part of the image later. Normal customization packages that just change
or add some configuration files should not be one-shot packages, they
don't require special tools and therefor its not use purging them to
remove their dependencies.
I don't even know if it makes really sense to allow multiple packages as
one-shot packages, but I did it because it might be useful in some
strange corner cases for someone and wasn't a big effort to do.
> If many, how
> to split customizations between packages?
All the customization, apart from locale configuration should be in
normal packages, however the user choose to do this. locale
configuration should be done with overwriting isar-cfg-localepurge
package or its files.
Maybe the name of that package is choosen poorly. I don't know.
> Or just describe the mechanism and leave the splitting decision to the user?
Yes. That would be useful. The user might want to mix and match
different configuration fragments contained in multiple configuration
packages.
> In the latter case, would that mean
> that in Isar, we'll by default provide only one package for all customizations?
I would think so. Maybe move the customization to a isar-cfg-example
package?
Claudius
>
> With kind regards,
> Baurzhan.
>
>
> On Mon, May 28, 2018 at 12:56:40PM +0200, claudius.heine.ext@siemens.com wrote:
>> From: Claudius Heine <ch@denx.de>
>>
>> Hi,
>>
>> I implemented Hennings suggestion to purge the one-shot packages in the
>> reverse order of the installation.
>>
>> Claudius
>>
>> Changes from v3:
>> - Purge one-shot packages in reverse order
>>
>> Changes from v2:
>> - Install one-shot package with a loop
>> - Rename '-y' apt parameter to '--yes'
>> - Move isar-cfg-localepurge files from /usr/local/etc to /usr/lib/
>>
>> Changes from v1:
>> - rebased to current next
>> - removed locale.nopurge setup in isar-bootstrap
>>
>> Claudius Heine (3):
>> isar-bootstrap|configscript: implement one shot config option
>> meta/isar-cfg-localepurge: added locale purge recipe
>> meta-isar/isar-image-base: switch use isar-cfg-localepurge
>>
>> .../images/files/debian-configscript.sh | 9 ------
>> .../images/files/raspbian-configscript.sh | 8 -----
>> .../recipes-core/images/isar-image-base.bb | 6 ++--
>> meta/classes/isar-bootstrap-helper.bbclass | 32 ++++++++++++++++---
>> .../isar-bootstrap/files/locale.nopurge | 10 ------
>> .../isar-bootstrap/isar-bootstrap.bb | 4 +--
>> .../isar-cfg-localepurge/files/locale.debconf | 12 +++++++
>> .../isar-cfg-localepurge/files/locale.gen | 1 +
>> .../isar-cfg-localepurge/files/postinst | 30 +++++++++++++++++
>> .../isar-cfg-localepurge.bb | 19 +++++++++++
>> 10 files changed, 94 insertions(+), 37 deletions(-)
>> delete mode 100644 meta/recipes-core/isar-bootstrap/files/locale.nopurge
>> create mode 100644 meta/recipes-support/isar-cfg-localepurge/files/locale.debconf
>> create mode 100644 meta/recipes-support/isar-cfg-localepurge/files/locale.gen
>> create mode 100644 meta/recipes-support/isar-cfg-localepurge/files/postinst
>> create mode 100644 meta/recipes-support/isar-cfg-localepurge/isar-cfg-localepurge.bb
>>
>> --
>> 2.17.0
>
--
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
prev parent reply other threads:[~2018-05-29 9:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 10:56 claudius.heine.ext
2018-05-28 10:56 ` [PATCH v4 1/3] isar-bootstrap|configscript: implement one shot config option claudius.heine.ext
2018-05-29 7:58 ` Maxim Yu. Osipov
2018-05-29 8:20 ` Claudius Heine
2018-05-29 10:56 ` Claudius Heine
2018-05-29 11:18 ` Maxim Yu. Osipov
2018-05-29 11:38 ` Claudius Heine
2018-05-28 10:56 ` [PATCH v4 2/3] meta/isar-cfg-localepurge: added locale purge recipe claudius.heine.ext
2018-05-28 10:56 ` [PATCH v4 3/3] meta-isar/isar-image-base: switch use isar-cfg-localepurge claudius.heine.ext
2018-05-29 8:00 ` [PATCH v4 0/3] One-shot configuration packages Baurzhan Ismagulov
2018-05-29 9:29 ` Claudius Heine [this message]
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=3e88b5b4-53b8-613d-ac35-00f8643fa232@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