488396 – sys-apps/systemd: (still) relies on Gentoo-specific python-config-X.Y

Bug 488396 - sys-apps/systemd: (still) relies on Gentoo-specific python-config-X.Y

Summary: sys-apps/systemd: (still) relies on Gentoo-specific python-config-X.Y

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	Normal major (vote)
Assignee:	Gentoo systemd Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	445592
	Show dependency tree

Reported:	2013-10-17 17:36 UTC by Michał Górny
Modified:	2014-09-04 13:02 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

2013-10-17 17:36:00 UTC

The upstream used naming for python-config is 'pythonX.Y-config'. Please fix your package to use that rather than relying on Gentoo-specific 'python-config-X.Y'.

This can be often fixed by removing some patch, sed or configure override.

Comment 1 Michał Górny archtester

2013-10-17 18:39:22 UTC

-9999 fixed.

Comment 2 Michał Górny archtester

2014-01-08 04:51:03 UTC

A modern note: if you're using python-r1, python-single-r1 or python-any-r1, it's not necessary to use 'python-config-X.Y' or 'pythonX.Y-config' anymore. The eclass puts a local symlink to proper 'python-config' variant in $PATH, so the build system can just take 'python-config' and it will get the version desired.

If the build system in question respects PYTHON and looks for appropriate pythonX.Y-config itself, great! If it doesn't, there's no need to hack it in. Just let it use python-config and the eclass will do the rest.

Comment 3 Michał Górny archtester

2014-09-04 13:02:27 UTC

Oh, and the releases having it are obviously long gone ;).