| 1 |
Hi, |
| 2 |
|
| 3 |
Unfortunately, the previous version of the patchset has caused |
| 4 |
regressions, so I had to revert the few last commits. Here's a little |
| 5 |
different approach that should be safe for existing ebuilds, |
| 6 |
and possibly less confusing to ebuild authors. |
| 7 |
|
| 8 |
Moving the ${BUILD_DIR}/install to D merge logic from |
| 9 |
distutils-r1_python_install into post-python_install broke ebuilds that |
| 10 |
relied on modifying the install tree in python_install. The new version |
| 11 |
leaves it in distutils-r1_python_install, so that existing ebuilds |
| 12 |
continue working. |
| 13 |
|
| 14 |
The different for 'no' mode is that distutils-r1_python_install needs |
| 15 |
to be called if you override python_install and expect the merging |
| 16 |
to happen. |
| 17 |
|
| 18 |
|
| 19 |
Michał Górny (7): |
| 20 |
distutils-r1.eclass: Move venv creation to post-compile |
| 21 |
distutils-r1.eclass: Future-proof python_install() for empty root |
| 22 |
distutils-r1.eclass: Move python_optimize call to post-install |
| 23 |
distutils-r1.eclass: Introduce DISTUTILS_USE_PEP517=no mode |
| 24 |
dev-python/tomli: Use DISTUTILS_USE_PEP517=no |
| 25 |
dev-python/installer: Use DISTUTILS_USE_PEP517=no |
| 26 |
dev-python/gpep517: Use DISTUTILS_USE_PEP517=no |
| 27 |
|
| 28 |
dev-python/gpep517/gpep517-6-r1.ebuild | 41 ++++++ |
| 29 |
.../installer/installer-0.5.1-r1.ebuild | 37 +++++ |
| 30 |
dev-python/tomli/tomli-2.0.1-r1.ebuild | 36 +++++ |
| 31 |
eclass/distutils-r1.eclass | 135 ++++++++++++------ |
| 32 |
4 files changed, 206 insertions(+), 43 deletions(-) |
| 33 |
create mode 100644 dev-python/gpep517/gpep517-6-r1.ebuild |
| 34 |
create mode 100644 dev-python/installer/installer-0.5.1-r1.ebuild |
| 35 |
create mode 100644 dev-python/tomli/tomli-2.0.1-r1.ebuild |
| 36 |
|
| 37 |
-- |
| 38 |
2.35.1 |
Archives