[poky] Systemd on Sumo without python3(runtime)

[matthew stanger]

Hi Ross,

Thanks for the reply. It seems running 'bitbake -g systemd' yields:
"systemd" -> "opkg-utils"
"opkg-utils" -> "python3"

I actually used a previous ML post about this from you to address that
aspect (https://lists.yoctoproject.org/pipermail/poky/2016-January/010342.html).
However I still don't understand why opkg-utils are listed as
dependencies for systemd. I do have opkg as part of my image via
'IMAGE_FEATURES+=package-managment' but I thought they should be
unrelated in this context?
On Mon, Oct 1, 2018 at 4:59 AM Burton, Ross <ross.burton at intel.com> wrote:
>
> On Sun, 30 Sep 2018 at 20:02, matthew stanger <stangerm2 at gmail.com> wrote:
> > I'm having trouble removing python3 from being installed as a runtime
> > package using the Sumo branch. Per the systemd(v237) build
> > spec's(https://github.com/systemd/systemd/blob/v237/README) line 167
> > there isn't runtime requirements for python3, only build time.
> >
> > It looks to me when running a .dot on the systemd dependencies that
> > python3 is being pulled in by 'meson' as a non'-native' dependency,
> > but this is where I'm lost. Could anyone clarify the logic here on how
> > to trim python3 to a native only dependency for systemd? Or is there
> > something fundamental I'm missing?
>
> Looking at the recipe I don't see where a Python 3 dependency comes
> from.  Have you verified that it's coming from systemd?
>
> Ross