From: Henning Schild <henning.schild@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 0-10 of 16 v2 4/8] meta: conf: use bitbake.conf from bitbake and apply local changes
Date: Mon, 21 Aug 2017 20:29:40 +0200 [thread overview]
Message-ID: <20170821202940.2f4b43c6@md1em3qc> (raw)
In-Reply-To: <20170821132539.GD8387@yssyq.radix50.net>
Am Mon, 21 Aug 2017 15:25:39 +0200
schrieb Baurzhan Ismagulov <ibr@radix50.net>:
> On Thu, Aug 03, 2017 at 01:55:53PM +0200, Henning Schild wrote:
> > force isar to always use a bitbake.conf from its bitbake
> > the diff went into a file that needs to be looked at later
>
> Applied with comment amendments, thanks.
Ok.
> Alex has updated the commit comment to reflect also the motivation
> for the change. In the commit comment, please use complete sentences
> (first cap, period at the end).
Yes i have seen that.
> We had considered the split configuration in the beginning and have
> seen that 1. Yocto forks it, and 2. bitbake doesn't seem to support
> reading both by itself. These were the reasons why we also forked the
> file.
>
> (1) might be caused by the fact that there are no major bitbake users
> except Yocto, so both are possibly not clearly separated. The
> separation has value for Isar, since it clearly shows what is
> different, that is why I've applied the patch.
>
> (2) is worse, as IMHO, bitbake should do that itself and it doesn't
> (https://github.com/ilbers/isar/issues/27). Concatenating configs is
> magic that Yocto users do not expect, and this has to be documented.
> Could you provide a patch for the manual?
No. You do not apply a patch directly to master if that creates an
issue, you could have asked me for a v3 instead. Please revert or
provide the patch to the manual yourself.
Henning
> With kind regards,
> Baurzhan.
>
next prev parent reply other threads:[~2017-08-21 18:29 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 11:55 [PATCH 0-10 of 16 v2 0/8] splitting the previous q Henning Schild
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 1/8] meta: classes: use base.bbclass from bitbake Henning Schild
2017-08-07 16:27 ` Alexander Smirnov
2017-08-08 8:52 ` Henning Schild
2017-08-08 9:39 ` Alexander Smirnov
2017-08-09 13:15 ` Henning Schild
2017-08-08 11:40 ` Jan Kiszka
2017-08-07 19:18 ` Alexander Smirnov
2017-08-08 8:43 ` Henning Schild
2017-08-08 14:02 ` Alexander Smirnov
2017-08-08 14:15 ` Henning Schild
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 2/8] meta: isar-base: remove unused function Henning Schild
2017-08-07 19:36 ` Alexander Smirnov
2017-08-08 8:05 ` Henning Schild
2017-08-08 9:33 ` Alexander Smirnov
2017-08-08 12:08 ` Henning Schild
2017-08-08 12:29 ` Alexander Smirnov
2017-08-08 13:12 ` Henning Schild
2017-08-08 13:24 ` Alexander Smirnov
2017-08-08 14:21 ` Henning Schild
2017-08-21 23:05 ` Baurzhan Ismagulov
2017-08-08 13:47 ` Alexander Smirnov
2017-08-08 14:17 ` Henning Schild
2017-08-21 22:26 ` Baurzhan Ismagulov
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 3/8] remove redundant variable THISDIR Henning Schild
2017-08-07 19:30 ` Alexander Smirnov
2017-08-08 8:02 ` Henning Schild
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 4/8] meta: conf: use bitbake.conf from bitbake and apply local changes Henning Schild
2017-08-07 19:37 ` Alexander Smirnov
2017-08-21 13:25 ` Baurzhan Ismagulov
2017-08-21 18:29 ` Henning Schild [this message]
2017-08-22 11:31 ` Baurzhan Ismagulov
2017-08-22 12:45 ` Henning Schild
2017-08-22 15:31 ` Baurzhan Ismagulov
2017-08-22 18:55 ` Henning Schild
2017-08-23 11:31 ` Baurzhan Ismagulov
2017-08-23 11:46 ` Henning Schild
2017-08-27 23:46 ` Baurzhan Ismagulov
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 5/8] meta: conf: clean up local bitbake config Henning Schild
2017-08-07 19:37 ` Alexander Smirnov
2017-08-21 19:55 ` Baurzhan Ismagulov
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 6/8] classes: move fetch and unpack into isar-base Henning Schild
2017-08-07 19:40 ` Alexander Smirnov
2017-08-08 8:00 ` Henning Schild
2017-08-08 9:30 ` Alexander Smirnov
2017-08-08 12:01 ` Henning Schild
2017-08-21 20:27 ` Baurzhan Ismagulov
2017-08-22 8:19 ` Henning Schild
2017-08-22 10:18 ` Baurzhan Ismagulov
2017-08-22 10:44 ` Henning Schild
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 7/8] meta: dpdk use [dirs] directive instead of mkdir Henning Schild
2017-08-07 19:41 ` Alexander Smirnov
2017-08-21 20:33 ` Baurzhan Ismagulov
2017-08-03 11:55 ` [PATCH 0-10 of 16 v2 8/8] meta: dpkg: reorder and rename do_install to install in addtask Henning Schild
2017-08-07 19:41 ` Alexander Smirnov
2017-08-21 20:42 ` Baurzhan Ismagulov
2017-08-07 19:44 ` [PATCH 0-10 of 16 v2 0/8] splitting the previous q Alexander Smirnov
2017-08-08 8:45 ` Henning Schild
2017-08-08 9:43 ` Alexander Smirnov
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=20170821202940.2f4b43c6@md1em3qc \
--to=henning.schild@siemens.com \
--cc=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