From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 1/4] isar-image-base: introduce and use isar-image class
Date: Fri, 9 Nov 2018 14:42:35 +0100 [thread overview]
Message-ID: <20181109134235.GD17039@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20181029161303.7410-2-Cedric_Hombourger@mentor.com>
On Mon, Oct 29, 2018 at 05:13:00PM +0100, Cedric Hombourger wrote:
> A second objective behind this change is for recipes (.bb files) to only
> contain meta-data: no code/scripts.
...
> .../files => conf/distro}/debian-configscript.sh | 0
> .../files => conf/distro}/raspbian-configscript.sh | 0
The scripts have been deliberately placed alongside the recipe till we have
enough evidence that they are 1. universal enough (serve 80% of users as they
are) and 2. readily overridable (so that users are not forced to copy-paste the
whole thing to remove an undesired customization). If they contain generic
pluggable parts selectively reusable downstream, that could be useful. Besides,
I find having scripts under conf/ not very intuitive. What is the problem with
having the scripts in the recipe?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2018-11-09 13:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 16:12 [PATCH 0/4] add support for OE's ROOTFS_*_COMMAND 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 [this message]
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
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=20181109134235.GD17039@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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