From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 13/14] connman: do nothing in qemu, do not touch eth0
Date: Tue, 11 Jan 2022 11:08:15 +0000 [thread overview]
Message-ID: <8993e498bf8d266832f911b7b2c7263ccaf418e7.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj9jRkc32Xm7PevLuFEgLOxTdaq7bYGu9=_gU3PitT7_-A@mail.gmail.com>
On Tue, 2022-01-11 at 12:02 +0100, Alexander Kanavin wrote:
> On Tue, 11 Jan 2022 at 11:55, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > > +# Kernel IP-Config is perfectly capable of setting up networking passed
> > > in
> > via ip=
> > > +do_install:append:qemuall() {
> > > + mkdir -p ${D}${sysconfdir}/default
> > > + echo "export EXTRA_PARAM=\"-I eth0\"" >
> > ${D}${sysconfdir}/default/connman
> > > +}
> >
> > This means connman becomes machine specific, you can't do that. This would
> > need
> > to be done in the connman-conf recipe.
>
> I'm not sure I follow - the above instructs connman to ignore eth0 inside qemu
> (and only inside qemu), why is that problematic?
The data above is inserted into /etc/default/connman in the connman package
itself. That package is installed into deploy/XXX/<tunearch>/connman.YYY. That
is not the machine specific package directory.
Or in different words, if I build connmand for a qemu machine, then build
connman for a machine with the same tune that isn't qemu, command rebuilds but
installs the package to the same location. This is not allowed.
Machine specific data (in this case qemu specific) shouldn't be in general
packages. This goes against yocto-check-layer and YP-Compatibility.
Cheers,
Richard
next prev parent reply other threads:[~2022-01-11 11:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 22:27 [PATCH 01/14] python3: drop unneeded multiprocessing module patch Alexander Kanavin
2022-01-09 22:27 ` [PATCH 02/14] ruby: disable rdoc due to non-reproducibility Alexander Kanavin
2022-01-09 22:27 ` [PATCH 03/14] rust-llvm: apply the same reproducibility patch as for llvm proper Alexander Kanavin
2022-01-09 22:27 ` [PATCH 04/14] busybox: update 1.34.1 -> 1.35.0 Alexander Kanavin
2022-01-10 15:09 ` [OE-core] " akuster808
[not found] ` <16C8F145D420B770.27414@lists.openembedded.org>
2022-01-10 15:10 ` Armin Kuster
2022-01-09 22:27 ` [PATCH 05/14] systemd: update 249.7 -> 250.1 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 06/14] python3-numpy: update 1.21.4 -> 1.22.0 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 07/14] mdadm: update 4.1 -> 4.2 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 08/14] librsvg: update 2.52.4 -> 2.52.5 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 09/14] libportal: update 0.4 -> 0.5 Alexander Kanavin
2022-01-09 22:27 ` [PATCH 10/14] epiphany: make libportal optional, and move it to meta-oe Alexander Kanavin
2022-01-10 18:43 ` [OE-core] " Khem Raj
2022-01-10 18:49 ` Alexander Kanavin
2022-01-10 18:57 ` Khem Raj
2022-01-10 19:18 ` Alexander Kanavin
2022-01-10 20:54 ` Khem Raj
2022-01-11 7:49 ` Khem Raj
2022-01-11 8:48 ` Alexander Kanavin
2022-01-11 19:44 ` Khem Raj
2022-01-09 22:27 ` [PATCH 11/14] qemuboot/runqemu: fully form the ip= kernel parameter Alexander Kanavin
2022-01-09 22:27 ` [PATCH 12/14] parselogs: add a couple systemd false positives Alexander Kanavin
2022-01-09 22:27 ` [PATCH 13/14] connman: do nothing in qemu, do not touch eth0 Alexander Kanavin
2022-01-11 10:54 ` [OE-core] " Richard Purdie
2022-01-11 11:02 ` Alexander Kanavin
2022-01-11 11:08 ` Richard Purdie [this message]
2022-01-11 11:10 ` Alexander Kanavin
2022-01-11 11:15 ` Richard Purdie
2022-01-09 22:27 ` [PATCH 14/14] systemd-boot: restore reproducibility Alexander Kanavin
2022-01-10 13:59 ` [OE-core] [PATCH 01/14] python3: drop unneeded multiprocessing module patch Richard Purdie
2022-01-10 14:21 ` Alexander Kanavin
2022-01-10 14:23 ` 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=8993e498bf8d266832f911b7b2c7263ccaf418e7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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