[poky] Systemd on Sumo without python3(runtime)

[Burton, Ross]

I'm still not sure what your actual problem is.  If Py3 is just
appearing during a build, that's expected.  If it's in the image and
you don't want it in the image, the easy way to find out what is
pulling it in is to remove it inside the image using the package
manager.  That will then tell you want will break if you remove it.

Ross
On Mon, 1 Oct 2018 at 16:36, matthew stanger <stangerm2 at gmail.com> wrote:
>
> Ahh thanks, that explains that. I'm not aware that I'm pulling in Py3
> as part of my image but I must be somewhere. I'm just using a trimmed
> version of the console-image.bb of the Raspberry Pi meta-layer by
> Scott Ellis (https://github.com/jumpnow/meta-rpi/blob/sumo/images/console-image.bb)
> where I changed out sysvinit for systemd in the local.conf and am only
> building the $(CORE_OS) targets [kernel-modules, openssh
> openssh-keygen openssh-sftp-server, packagegroup-core-boot,
> term-prompt, tzdata], so I'm not sure where the Py3 part is being set.
> I know you're busy so what would be the best way in this case for me
> to track down where this is set?
> On Mon, Oct 1, 2018 at 9:05 AM Burton, Ross <ross.burton at intel.com> wrote:
> >
> > Well, -g shows you *build* dependencies, not target.  Build
> > dependencies are recipes, whereas target dependencies will be
> > packages.
> >
> > I see systemd just depending on update-alternatives-opkg, part of
> > opkg-utils but without the Python dependency.
> >
> > Have you demonstrated that Py3 is part of your *images*?
> >
> > Ross
> > On Mon, 1 Oct 2018 at 15:55, matthew stanger <stangerm2 at gmail.com> wrote:
> > >
> > > 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