Bug 532014

Summary:	util-linux/util-linux: PYTHON_SINGLE_TARGET is not respected unless USE=python is enabled
Product:	Gentoo Linux	Reporter:	Zac Medico <zmedico>
Component:	[OLD] Core system	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	chutzpah, pacho, python
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Zac Medico gentoo-dev

2014-12-09 00:51:13 UTC

PYTHON_SINGLE_TARGET is not respected unless USE=python is enabled. This is bad for ebuilds that depend on python_single_target_* USE flags, because they don't work unless USE=python is enabled.

I suggest additions to REQUIRED_USE as follows:

python_single_target_python2_7? ( python )
python_single_target_python3_2? ( python )
python_single_target_python3_3? ( python )
python_single_target_python3.4? ( python )

Comment 1 Pacho Ramos gentoo-dev

2015-01-18 09:42:07 UTC

This looks to affect to also current stable version. I am unsure if that ebuilds shouldn't then depend on util-linux[python] instead of needing to add (and update) the python_single_target_python2_7? ( python ) logic in ebuild :/

Comment 2 Michał Górny archtester

2015-01-18 09:47:11 UTC

That doesn't make sense at all. Why would you require any specific implementation choice when you don't use Python at all?

Comment 3 Zac Medico gentoo-dev

2015-01-18 10:09:19 UTC

(In reply to Michał Górny from comment #2)
> That doesn't make sense at all. Why would you require any specific
> implementation choice when you don't use Python at all?

The python_single_target_* flags are meaningless unless USE=python is enabled, and REQUIRED_USE will allow you to encapsulate this logic in the util-linux ebuild, so that ebuilds which depend on the python_single_target_* flags aren't forced to be aware that util-linux happens to have a python flag. This makes dependency specifications more uniform, since ebuilds that have python_single_target_* flags may or may not have a python flag.

Comment 4 Michał Górny archtester

2015-01-18 10:40:58 UTC

(In reply to Zac Medico from comment #3)
> (In reply to Michał Górny from comment #2)
> > That doesn't make sense at all. Why would you require any specific
> > implementation choice when you don't use Python at all?
> 
> The python_single_target_* flags are meaningless unless USE=python is
> enabled, and REQUIRED_USE will allow you to encapsulate this logic in the
> util-linux ebuild, so that ebuilds which depend on the
> python_single_target_* flags aren't forced to be aware that util-linux
> happens to have a python flag. This makes dependency specifications more
> uniform, since ebuilds that have python_single_target_* flags may or may not
> have a python flag.

No, this will only force most of the Gentoo users to enable USE=python on util-linux.

If ebuild doesn't have IUSE=python, then it should depend on util-linux[python,${PYTHON_USEDEP}]... what's the problem, again?

Comment 5 Zac Medico gentoo-dev

2015-01-18 11:04:27 UTC

(In reply to Michał Górny from comment #4)
> No, this will only force most of the Gentoo users to enable USE=python on
> util-linux.

Oh, because they have a global PYTHON_SINGLE_TARGET setting. So, it's actually a feature that python_single_target_* flags are meaningless without USE=python. I get it.

> If ebuild doesn't have IUSE=python, then it should depend on
> util-linux[python,${PYTHON_USEDEP}]... what's the problem, again?

Okay, that works for me. Thanks!