[poky] Systemd on Sumo without python3(runtime)

[matthew stanger]

Just to leave a clean paper trail. It was the
'IMAGE_FEATURES+=package-managment' in my local.conf, thus 'opkg'
needing (configurable)Py3 indirectly, and not systemd:
  "opkg" -> "libarchive"
  "libarchive" -> "libxml2"
  "libxml2" -> "python3"

With libxml2 being marked clearly in openembedded for Py3
(https://layers.openembedded.org/layerindex/recipe/80796/).

Cheers,
On Mon, Oct 1, 2018 at 10:10 AM Khem Raj <raj.khem at gmail.com> wrote:
>
> On Mon, Oct 1, 2018 at 8:34 AM 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?
>
> Generally its better to start of a known smaller images preferably
> from OE-core and then build on top by
> adding your own needs, building up is easier than tearing down in this
> case. The image you are basing of has a lot of stuff which can pull in
> py3 especially the dev packages.
>
> to sort out your case. enable buildhistory, then go into buildhistory folder.
> e.g. buildhistory/images/qemux86/musl/core-image-sato
> and then inspect depends-nokernel-nolibc-noupdate-nomodules.dot
> especially look for "python3" in RHS of -> marker
>
> that will give you the package on LHS which is asking for python3 then you
> can walk backwards from there.
>
> > 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
> > --
> > _______________________________________________
> > poky mailing list
> > poky at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/poky