This package still uses the legacy eclass code paths. These paths are deprecated and pose a significant maintenance cost. Please update the package to use PEP517 build mode. For more information, please see the Python Guide, particularly; https://projects.gentoo.org/python/guide/migration.html#migrating-to-pep-517-builds
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e25dc19957b596c0044aaaa3ef0c57dc55116c0a commit e25dc19957b596c0044aaaa3ef0c57dc55116c0a Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2023-07-08 14:59:59 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2023-07-08 18:41:41 +0000 dev-util/catalyst: use PEP517 build Closes: https://bugs.gentoo.org/909976 Signed-off-by: Ben Kohler <bkohler@gentoo.org> dev-util/catalyst/catalyst-3.0.22-r2.ebuild | 74 +++++++++++++++++++++++++++++ dev-util/catalyst/catalyst-9999.ebuild | 6 ++- 2 files changed, 78 insertions(+), 2 deletions(-)
[Adding this comment en-masse, sorry for the noise, but it's important.) 1. Please take particular care to check file diffs before/after, possibly using `iwdevtools`. Keep a particular eye out for e.g. config files now missing from /etc and instead being in /usr/lib/python*/site-packages, etc. 2. Please make sure to do the migration in a new revision in ~arch, partly because of 1.
