From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Luca Bocassi <luca.boccassi@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3] util-linux: split uuid in separate recipe to allow bootstrapping
Date: Thu, 10 Dec 2020 15:52:46 +0000 [thread overview]
Message-ID: <2d012b8dcd17962239264152e6969edda609e16c.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201123132823.3996355-1-luca.boccassi@gmail.com>
On Mon, 2020-11-23 at 13:28 +0000, Luca Bocassi wrote:
> From: Luca Boccassi <luca.boccassi@microsoft.com>
>
> In v2.35 util-linux gained an (optional) build
> dependency on libcryptsetup. But libcryptsetup build-depends on
> util-linux for blkid (optional, can be disabled) and uuid (mandatory).
> Split out util-linux-uuid in a different recipe to break the cycle.
>
> Add a packageconfig switch (disabled by default) to allow using the
> new dependency.
>
> https://github.com/karelzak/util-linux/pull/898
>
> Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
> ---
> v1: util-linux 2.35 is not out yet, but I'd like to get the preparatory work
> underway as I'm not sure if this is the best approach or if there are
> alternatives. Suggestions and comments very welcome. Thanks!
> v2: changed packages names to reflect old ones (eg: libuuid1 -> util-linux-libuuid)
> and leave uuid build enable in main recipe to allow for uuidgen build to happen,
> as it does not have its own autoconf switch. Delete the library manualy from
> the main recipe after build instead, and add dependency.
> Might help to break loop python3 -> util-linux -> libselinux -> python3, as it's
> only libuuid that is needed, see https://lists.yoctoproject.org/g/yocto/message/47570
> v3: rebased and refactored to have a common util-linux.inc file
>
I'm afraid this causes do_package_qa errors in basic testing:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1668
I am worried about this change as we're starting to see a number of
circular dependencies in util-linux (there is a new bug about the
pylibmount PACKAGECONFIG option too), maybe we should flag this
upstream?
Multiple recipes like this usually turn into a maintenance nightmare
unfortunately which is part of my reluctance to go in this direction,
not sure we have any choice though.
Cheers,
Richard
next prev parent reply other threads:[~2020-12-10 15:52 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 20:13 [PATCH] util-linux: split uuid in separate recipe to allow bootstrapping luca.boccassi
2019-12-05 23:29 ` Ross Burton
2019-12-09 16:24 ` [PATCH v2] " luca.boccassi
2020-11-23 13:28 ` [PATCH v3] " Luca Bocassi
2020-12-10 15:52 ` Richard Purdie [this message]
2020-12-10 18:47 ` [OE-core] " Luca Boccassi
2020-12-10 20:04 ` Richard Purdie
2020-12-11 9:51 ` Luca Boccassi
2020-12-11 16:54 ` Richard Purdie
2020-12-14 16:32 ` Luca Boccassi
2020-12-10 18:46 ` [PATCH v4] " Luca Bocassi
2021-01-19 20:52 ` Richard Purdie
2021-01-19 23:13 ` [OE-core] " Paul Eggleton
2021-01-19 23:23 ` Richard Purdie
2021-01-19 23:28 ` Paul Eggleton
2021-02-25 15:31 ` Luca Bocassi
2021-02-25 15:30 ` [PATCH v5] " Luca Bocassi
2021-02-26 19:02 ` [OE-core] " Khem Raj
2021-03-02 19:01 ` Luca Bocassi
2021-02-27 14:52 ` Alexandre Belloni
2021-02-27 15:08 ` Alexandre Belloni
2021-02-27 15:15 ` Alexandre Belloni
2021-03-02 17:31 ` Luca Bocassi
2021-03-02 18:49 ` Alexandre Belloni
2021-03-03 22:30 ` Richard Purdie
2021-03-04 12:05 ` Luca Bocassi
2021-03-04 12:27 ` [PATCH v6] " Luca Bocassi
2021-03-05 0:13 ` Richard Purdie
2021-03-05 11:03 ` Luca Bocassi
2021-03-05 11:02 ` [PATCH v7] " Luca Bocassi
2021-03-08 19:29 ` Richard Purdie
2021-03-09 11:07 ` Luca Bocassi
2021-03-09 11:18 ` [OE-core] " Kory Maincent
2021-03-09 13:26 ` Luca Bocassi
2021-03-09 13:47 ` Kory Maincent
2021-03-09 13:48 ` Richard Purdie
2021-03-09 13:56 ` Luca Bocassi
2021-03-09 11:13 ` [PATCH v8] " Luca Bocassi
2021-03-09 13:56 ` [PATCH v9] " Luca Bocassi
2021-03-09 23:43 ` Richard Purdie
2021-03-10 18:28 ` Luca Bocassi
2021-03-11 10:15 ` Luca Bocassi
2021-03-11 10:31 ` Richard Purdie
2021-03-11 14:37 ` Luca Bocassi
2021-03-11 14:38 ` [PATCH v10] " Luca Bocassi
2021-03-11 14:44 ` Richard Purdie
2021-03-11 15:10 ` Luca Bocassi
2021-03-11 15:09 ` [PATCH v11] " Luca Bocassi
2021-03-14 22:10 ` Richard Purdie
2021-03-15 10:44 ` Luca Bocassi
2021-03-15 10:49 ` Richard Purdie
2021-03-15 11:50 ` Luca Bocassi
2021-03-15 12:21 ` Richard Purdie
2021-03-15 13:04 ` Luca Bocassi
2021-03-15 13:55 ` [OE-core] " Martin Jansa
2021-03-15 13:57 ` Richard Purdie
[not found] ` <166C88B2CBAB1BAF.20509@lists.openembedded.org>
2021-03-15 21:51 ` Richard Purdie
2021-03-24 16:52 ` Scott Branden
2021-03-24 17:03 ` Luca Boccassi
2021-03-24 17:37 ` Richard Purdie
2021-03-24 17:52 ` Luca Bocassi
2021-03-25 9:17 ` Oleksiy Obitotskyy
2021-03-25 9:34 ` Richard Purdie
2021-03-25 9:48 ` Luca Bocassi
2021-03-25 14:22 ` Peter Kjellerstedt
2021-03-25 14:27 ` Richard Purdie
2021-03-25 15:45 ` Luca Bocassi
2021-03-25 16:01 ` Khem Raj
2021-03-25 16:19 ` Peter Kjellerstedt
2021-03-25 16:51 ` Richard Purdie
2021-03-26 18:06 ` Peter Kjellerstedt
2021-03-26 18:12 ` Richard Purdie
2021-03-26 18:22 ` Andre McCurdy
2019-12-09 16:33 ` [PATCH] " Luca Boccassi
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=2d012b8dcd17962239264152e6969edda609e16c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=luca.boccassi@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox