From: "Andreas Müller" <schnitzeltony@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>, Joshua Watt <JPEWhacker@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC PATCH 14/14] layer.conf: Extend recipes not to install without explict dependencies
Date: Mon, 18 Oct 2021 18:59:04 +0200 [thread overview]
Message-ID: <CALbNGRTxs26=VO7DmHe41QOgy=acByprKzUSzenZpYSfdJ_z_A@mail.gmail.com> (raw)
In-Reply-To: <CA+chaQctdc_sUpmvs-vN0RatkOx=JoMnVZCqY+WjxGfXOYX0fQ@mail.gmail.com>
On Mon, Oct 18, 2021 at 4:12 PM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> On Mon, Oct 18, 2021 at 1:50 AM Andreas Müller <schnitzeltony@gmail.com> wrote:
>>
>> On Fri, Oct 1, 2021 at 4:17 PM Martin Jansa <Martin.Jansa@gmail.com> wrote:
>> >
>> > FWIW: I've fixed some bigger layers where pkgconfig was causing quite a few build failures,
>> >
>> Had an off-oe time due to heavy work load.
>> Think this one is the reason for the pkgconfig patch flood. You are
>> aware that there are packages not failing at build time for missing
>> pkgconfig but build output is different and bugs will pop up at
>> runtime.
>>
>> To avoid responsible maintainers have to go through EVERY recipe (and
>> combination of PACKAGECONFIGs) and check if builds are still as
>> expected - Can't believe it!
>
>
> Not sure why this seems targeted to me.
It was not targeted to you - just responded all in the last post - sorry
Andreas
>
> Yes I've tried to fix whatever issues this change caused in my world builds and I'm partially responsible for pkgconfig patch flood, because I wanted layers like meta-ros/*, meta-qt5, meta-qt6, meta-webosose/* to stay compatible with oe-core whenever this change from RP is merged to master.
>
> I've also tried to compare buildhistory and image content (for ros-image-world with ros1-melodic) to see if I can spot more cases of non-fatal build output changes as in collada-dom and unfortunately there is a lot of noise in buildhistory (due to many recipes included in this image not really build-reproducible), so I've used mostly installed-package-sizes.txt file to spot 2 more recipes where the size was different (but both don't seem to be caused by pkgconfig-native in the end).
>
> I did both builds from scratch without sstate, so I would assume that it will catch all possible cases, but surprisingly just yesterday I've caught another missing pkgconfig-native in one of meta-ros1-melodic recipes (caught in kirkstone based build - while before I was testing on top of a bit older honister with this change cherry-picked just for test - to prepare recipes to be future-proof for kirkstone).
>
> Regards,
next prev parent reply other threads:[~2021-10-18 16:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 12:46 [PATCH 01/14] vim: Backport fix for CVE-2021-3770 Richard Purdie
2021-09-20 12:46 ` [PATCH 02/14] libgcrypt: Upgrade 1.9.3 -> 1.9.4 Richard Purdie
2021-09-20 12:46 ` [PATCH 03/14] sqlite3: Exclude CVE-2021-36690 from cve checks Richard Purdie
2021-09-20 12:46 ` [PATCH 04/14] recipes: Add missing pkgconfig inherit Richard Purdie
2021-09-20 12:46 ` [PATCH 05/14] lttng-tools: Add missing DEPENDS on bison-native Richard Purdie
2022-01-18 20:48 ` [OE-core] " Denys Dmytriyenko
2021-09-20 12:46 ` [PATCH 06/14] image/qemu: Add explict depends for qemu-helper addto_recipe_sysroot task Richard Purdie
2021-09-20 12:46 ` [PATCH 07/14] staging: Mark deploy an sstate task Richard Purdie
2021-09-20 12:46 ` [PATCH 08/14] sstate: Ensure deploy tasks don't pull in toolchains Richard Purdie
2021-09-20 12:46 ` [PATCH 09/14] sstate: Avoid deploy_source_date_epoch sstate when unneeded Richard Purdie
2021-09-20 12:46 ` [RFC PATCH 10/14] package_ipk/deb/rpm: Drop recursive do_build task dependencies Richard Purdie
2021-09-23 21:41 ` [OE-core] " Peter Kjellerstedt
2021-09-23 21:58 ` Richard Purdie
2021-09-24 4:50 ` Khem Raj
2021-09-24 7:58 ` Martin Jansa
2021-09-24 8:30 ` Richard Purdie
2021-09-24 17:20 ` Khem Raj
2021-09-20 12:46 ` [RFC PATCH 11/14] populate_sdk_base/images: Drop use of 'meta' class and hence do_build dependencies Richard Purdie
2021-10-27 2:43 ` [OE-core] " ChenQi
2021-11-02 13:06 ` Richard Purdie
2021-09-20 12:46 ` [PATCH 12/14] buildtools-tarball/uninative-tarball/meta-ide-support: Drop useless meta class Richard Purdie
2021-09-20 12:46 ` [PATCH 13/14] meta: Drop useless class Richard Purdie
2021-09-20 12:46 ` [RFC PATCH 14/14] layer.conf: Extend recipes not to install without explict dependencies Richard Purdie
[not found] ` <16A68880435BB472.28512@lists.openembedded.org>
2021-09-20 12:48 ` [OE-core] " Richard Purdie
2021-09-20 13:34 ` Joshua Watt
2021-09-21 4:21 ` Khem Raj
2021-10-01 14:17 ` Martin Jansa
2021-10-17 23:50 ` Andreas Müller
2021-10-18 14:12 ` Martin Jansa
2021-10-18 14:29 ` Richard Purdie
2021-10-18 16:50 ` Andreas Müller
2021-10-18 16:59 ` Andreas Müller [this message]
2021-10-18 19:07 ` Konrad Weihmann
2021-10-18 21:08 ` Richard Purdie
[not found] ` <16A6887F33E2E04C.31899@lists.openembedded.org>
2021-09-20 12:51 ` [OE-core] [RFC PATCH 11/14] populate_sdk_base/images: Drop use of 'meta' class and hence do_build dependencies Richard Purdie
2021-09-20 16:32 ` Khem Raj
2021-09-20 20:02 ` Richard Purdie
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='CALbNGRTxs26=VO7DmHe41QOgy=acByprKzUSzenZpYSfdJ_z_A@mail.gmail.com' \
--to=schnitzeltony@gmail.com \
--cc=JPEWhacker@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.