If I want to override the python3-manifest.json part of the python3 recipe; how
should I do that from a layer of my own?
I first attempted to add a custom python3-manifest.json in my custom layer that
has higher BBFILE_PRIORITY than poky. I observe that my json is installed to
the $WORKSPACE, but package splitting is still done using the .json from poky
meta layer...
The way that the manifest is included from python3.bb (rocko-warrior) seems to
not allow custom manifest?
filename = os.path.join(d.getVar('THISDIR'), 'python3', 'python3-manifest.json')
I could not find any documentation on how customization is supposed to work
after the introduction of the JSON manifest.
I want to be able to remove rdepends on python3-email when installing
python3-netclient (in sumo), as my use of netclient actually does not use email
(and email has many dependancies that make including it add a large footprint
to my image).
I did find a hack to be able to do what I want, but it is not very clean. Is
there a cleaner solution?
Hack:
In my custom layer create a modified copy of the JSON manifest in
recipes-devtools/python/python3/python3-manifest.json
For sumo in my custom layer with higher prio than poky create a
recipes-devtools/python/python3_3.5.5.bb file with the following content:
require ../../../../poky/meta/recipes-devtools/python/python3_3.5.5.bb
# Adapted JSON manifest is found from THISDIR, so no need to add custom
${THISDIR}/python3 to FILESEXTRAPATHS
FILESEXTRAPATHS_prepend :=
"${THISDIR}/../../../../poky/meta/recipes-devtools/python/python3:"
/Regards Sander
This email message and any attachments may contain confidential information and
may be privileged. If you are not the intended recipient or otherwise not
authorized to receive this message, you are prohibited to use, copy, disclose
or take any action based on this email or any information contained herein. If
you are not the intended recipient, please advise the sender immediately by
replying to this email and permanently delete this message and any attachments
from your system.
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
