909891 – app-portage/layman: needs to use PEP517 build (DistutilsNonPEP517Build)

Bug 909891 - app-portage/layman: needs to use PEP517 build (DistutilsNonPEP517Build)

Summary: app-portage/layman: needs to use PEP517 build (DistutilsNonPEP517Build)

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All All

Importance:	Normal normal
Assignee:	Layman Overlay Manager project

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	pep517-porting
	Show dependency tree

Reported:	2023-07-08 06:46 UTC by Michał Górny
Modified:	2023-09-08 08:27 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michał Górny archtester

2023-07-08 06:46:24 UTC

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

Comment 1 Sam James archtester

2023-07-08 20:40:51 UTC

[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.

Comment 2 David Seifert gentoo-dev

2023-09-08 08:27:09 UTC

Removed in commit abfaed0b3460e638410c0fd74783f8d292d63afc