[OE-core] [PATCH] Yocto: Install full set of python modules in Qt SDK toolchain

[Burton, Ross]

On 21 September 2014 at 17:02, Marek Vasut <marex at denx.de> wrote:

> -TOOLCHAIN_HOST_TASK ?= "nativesdk-packagegroup-sdk-host
> packagegroup-cross-
> canadian-${MACHINE}"
> +TOOLCHAIN_HOST_TASK ?= "                               \
> +       nativesdk-packagegroup-sdk-host                 \
> +       packagegroup-cross-canadian-${MACHINE}          \
> +       nativesdk-python-modules
>

Thanks to Laszlo for pinging this.  We fixed a similar problem in the
buildtools tarball by pulling in python-modules but the situation was
different there - the buildtools tarball always contained some of Python so
it's logical to make it pull in all of python.

It's nativesdk-packagegroup-sdk-host that's pulling in parts of Python via
it's dependency on smartpm.  This makes me think we need two changes here:

1) The toolchain should contain the packaging tools for the selected
packaging format of the images, not just smartpm.  So a SDK for a
opkg-based image should be shipping opkg, not smartpm.

2) Toolchains should either ship no Python or all Python, because dropping
a partial Python into $PATH breaks user's expectations (the same argument
that was used for the buildtools).  Not sure how to do this though, maybe
the construction should inspect the installed package list and if anything
Python was installed, ensure python-modules is also installed.

Comments?

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20141201/c0da070d/attachment-0002.html>