Date: Tue, 18 Jul 2023 23:30:58 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 270510] python.mk: remove setuptools from RUN_DEPENDS Message-ID: <bug-270510-7788-RtfDhlC0qq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270510-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-270510-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270510 Charlie Li <vishwin@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |272584 Blocks|272584 | --- Comment #4 from Charlie Li <vishwin@freebsd.org> --- Quick glean from exp-run and some RUN_DEPENDS snooping reveal that setuptools_scm, hatch-vcs et al specify setuptools in RUN_DEPENDS. Technica= lly correct per upstream package metadata, but causes environment pollution with our build processes. Still need to check for any pkg_resources consumers bu= t I doubt any exist anymore. For documentation purposes (will add to wiki later): RUN_DEPENDS should never contain ${PY_SETUPTOOLS} unless the port in questi= on is a leaf port (ie no further consumers). Those ports that specify setuptoo= ls as a runtime dependency in the Python package metadata should have their consumers specify them instead. The ${PY_SETUPTOOLS} dependency line return= ed is only correct for the port it is used in. As different setuptools versions cannot exist concurrently in the same environment (chroot, jail, Python vir= tual environment, etc), it is essential to prevent environment pollution via RUN_DEPENDS, especially when multiple ports in a dependency chain differ between USE_PYTHON=3Dpep517 and USE_PYTHON=3Ddistutils. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272584 [Bug 272584] devel/py-attrs: Fix build with planned changes to RUN_DEPENDS = in Mk/Uses/python.mk --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270510-7788-RtfDhlC0qq>