Commit Graph
2 Commits
Author SHA1 Message Date
Ricardo Silva c06be20b24 pycrypto: Add recipe to have support on python3
The pycrypto module sources can be used for both python2 and python3,
but a recipe for python3 was missing, so add it.

Additionally, since the sources (and thus the patches) are shared
between both versions, move the SRC_URI (same on both recipes) to the
common 'python-pycrypto.inc' file, to avoid duplication.

Also, to use the same patch files for both python2 and python3 without
having to duplicate them over 2 folders, change 'python-pycrypto.inc' so
that FILESEXTRAPATHS is prepended with the 'python-pycrypto' local dir
for both versions instead of having that dir named after the package
name '${PN}'.

The python3 recipe is basically the same as for python2, but using
distutils3 instead.

Signed-off-by: Ricardo Silva <rjpdasilva@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2018-01-16 21:38:09 -08:00
Ricardo Silva a5c7c4746e pyinotify: Fix support for different python versions
The runtime dependencies for pyinotify are defined in
python-pyinotify.inc file, which gets included from both the python2 and
the python3 recipes for pyinotify.

Since the include file is used for both python2 and python3 recipes, it
must use the '${PYTHON_PN}-' prefix instead of just 'python-' for
listing the dependencies in RDEPENDS, otherwise it is forcing python2
modules to be selected from a python3 recipe, so fix that.

For example, use '${PYTHON_PN}-threading' instead of 'python-threading'
for specifying a dependency from the 'threading' module.

While at it, also use line separation and indentation on RDEPENDS for
better readability.

Signed-off-by: Ricardo Silva <rjpdasilva@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2018-01-16 21:37:33 -08:00