summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/libical
diff options
context:
space:
mode:
authorRoss Burton <ross@burtonini.com>2022-03-04 11:55:25 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-03-05 10:45:13 +0000
commit47905882113e2905a8fc9664c5ab338e038c533b (patch)
treeec918c8b694417bc1ab8272088e1bdada316ab40 /meta/recipes-support/libical
parenta25c07622502727ca1b0e01d32127b57f75d28fb (diff)
downloadpoky-47905882113e2905a8fc9664c5ab338e038c533b.tar.gz
classes: add setuptools3_legacy
Following a good discussion with PyPA upstream[1] the migration of the setuptools3.bbclass to use bdist_wheel+pip turns out to be more complex than thought. Essentially, we're midway through a lot of changes: the future of Python packaging is wheels and pip, but those by design are not as flexible as traditional distutils and setup.py. Specifically, with traditional distutils the package can implement its own install task and write arbitrary files (such as init scripts). With wheels this is explicity impossible, so packages that do this cannot use the new setuptools class and must continue to use the build/install tasks as before. This class is the old setuptools behaviour, bought back. However, as distutils and the setuptools install task are both deprecated and will soon be removed entirely, any users of this class should be moving to an alternative build tool, be it a modern Python tool which works with wheels, or a non-Pythonic tool such as Meson. [1] https://github.com/pypa/packaging-problems/issues/576 (From OE-Core rev: 341d2b35986e48e4954c591be8bc037a5557452a) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-support/libical')
0 files changed, 0 insertions, 0 deletions