From: Henning Schild <henning.schild@siemens.com>
To: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/4] add support for OE's ROOTFS_*_COMMAND
Date: Tue, 30 Oct 2018 10:25:46 +0100 [thread overview]
Message-ID: <20181030102546.6f84f930@md1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <DD28FE24-E40F-4B41-885D-B9C59D688DDB@mentor.com>
Am Mon, 29 Oct 2018 16:55:10 +0000
schrieb "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>:
> Sure thing. This will allow us to generate license/package manifests
> like Yocto does amongst other things (eg rootfs optimization
> functions). In other words system wide tweaks. The former is the
> subject of an upcoming patch series.
rootfs optimization functions sounds very much like hacking your way
around the golden rule i mentioned earlier. And since people will abuse
such a mechanism it is best to not introduce it.
For the license manifests ... that sounds interesting indeed but will
likely not require such a generic mechanism.
I guess concrete examples would be useful. But looking just at the
mechanism without such examples, i am strongly against merging that
code.
Henning
> Sent from a mobile
>
> > On 29 Oct 2018, at 17:45, Henning Schild
> > <henning.schild@siemens.com> wrote:
> >
> > Hey,
> >
> > could you please elaborate on why this is needed and what you want
> > to do with it? I suspect there are already other ways of doing what
> > you might want to do.
> >
> > One golden rule is that _everything_ inside the rootfs comes from
> > a .deb package. If you need to execute scripts, go for post/pre inst
> > etc.
> >
> > Henning
> >
> > Am Mon, 29 Oct 2018 17:12:59 +0100
> > schrieb Cedric Hombourger <Cedric_Hombourger@mentor.com>:
> >
> >> OpenEmbedded allows custom functions to be called at various
> >> stages of the root file-system generation process. Add similar
> >> capabilities to Isar.
> >>
> >> Cedric Hombourger (4):
> >> isar-image-base: introduce and use isar-image class
> >> isar-image: refactor do_rootfs()
> >> base: add 'lib' folder of each layer to python's module search
> >> path isar-image: add support for OE's ROOTFS_*_COMMAND
> >>
> >> doc/user_manual.md | 43 +++++++++++
> >> meta-isar/classes/isar-image.bbclass | 89
> >> ++++++++++++++++++++++ .../files =>
> >> conf/distro}/debian-configscript.sh | 0 .../files =>
> >> conf/distro}/raspbian-configscript.sh | 0
> >> meta-isar/recipes-core/images/isar-image-base.bb | 57
> >> +------------- meta/classes/base.bbclass |
> >> 4 + meta/lib/oe/utils.py | 11 +++ 7
> >> files changed, 150 insertions(+), 54 deletions(-) create mode
> >> 100644 meta-isar/classes/isar-image.bbclass rename
> >> meta-isar/{recipes-core/images/files =>
> >> conf/distro}/debian-configscript.sh (100%) rename
> >> meta-isar/{recipes-core/images/files =>
> >> conf/distro}/raspbian-configscript.sh (100%) create mode 100644
> >> meta/lib/oe/utils.py
> >>
> >
next prev parent reply other threads:[~2018-10-30 9:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 16:12 Cedric Hombourger
2018-10-29 16:13 ` [PATCH 1/4] isar-image-base: introduce and use isar-image class Cedric Hombourger
2018-11-09 13:42 ` Baurzhan Ismagulov
2018-10-29 16:13 ` [PATCH 2/4] isar-image: refactor do_rootfs() Cedric Hombourger
2018-11-29 15:06 ` Jan Kiszka
2018-10-29 16:13 ` [PATCH 3/4] base: add 'lib' folder of each layer to python's module search path Cedric Hombourger
2018-10-29 16:13 ` [PATCH 4/4] isar-image: add support for OE's ROOTFS_*_COMMAND Cedric Hombourger
2018-10-29 16:45 ` [PATCH 0/4] " Henning Schild
2018-10-29 16:55 ` Hombourger, Cedric
2018-10-30 9:25 ` Henning Schild [this message]
2018-10-30 11:02 ` Hombourger, Cedric
2018-10-30 12:41 ` Henning Schild
2018-10-30 12:45 ` Hombourger, Cedric
2018-10-31 6:10 ` [PATCH v2 0/2] introduce isar-image class Cedric Hombourger
2018-10-31 6:10 ` [PATCH v2 1/2] isar-image-base: introduce and use " Cedric Hombourger
2018-10-31 6:10 ` [PATCH v2 2/2] isar-image: refactor do_rootfs() Cedric Hombourger
2018-10-31 6:39 ` [PATCH v2 0/2] introduce isar-image class Jan Kiszka
2018-10-31 6:51 ` chombourger
2018-11-01 11:43 ` Maxim Yu. Osipov
2018-11-09 13:26 ` Baurzhan Ismagulov
2018-11-01 10:13 ` [PATCH v3 1/2] isar-image-base: introduce and use " Cedric Hombourger
2018-11-01 10:13 ` [PATCH v3 2/2] isar-image: refactor do_rootfs() Cedric Hombourger
2018-11-07 13:20 ` Jan Kiszka
2018-11-08 7:59 ` Hombourger, Cedric
2018-11-08 8:28 ` Jan Kiszka
2018-11-07 18:45 ` Henning Schild
2018-11-07 19:46 ` Cedric Hombourger
2018-11-07 20:16 ` Cedric Hombourger
2018-11-08 6:52 ` Jan Kiszka
2018-11-08 8:13 ` Henning Schild
2018-11-07 13:07 ` [PATCH v3 1/2] isar-image-base: introduce and use isar-image class 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=20181030102546.6f84f930@md1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Cedric_Hombourger@mentor.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