Hey Ross,

The thing is that we do need them on the native sysroot, since when we are creating a new manifest, it uses python-native to do that, and it needs to match those files, if they dont exist, they end up in another package.

Alejandro

On 18 October 2017 at 22:07, Alejandro Hernandez <alejandro.hernandez@linux.intel.com> wrote:

@@ -77,8 +75,30 @@ do_install() {
                sed -i -e '1s|^#!.*|#!/usr/bin/env python3|' $PYTHSCRIPT
        done

-       # Tests are large and we don't need them in the native sysroot
-       rm ${D}${libdir}/python${PYTHON_MAJMIN}/test -rf
+        # Add a symlink to the native Python so that scripts can just invoke
+        # "nativepython" and get the right one without needing absolute paths
+        # (these often end up too long for the #! parser in the kernel as the
+        # buffer is 128 bytes long).
+        ln -s python3-native/python3 ${D}${bindir}/nativepython3

Is that rm of the tests redundant?

Ross