Gentoo Archives: gentoo-user

From: Andreas Fink <finkandreas@×××.de>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] PYTHON_SINGLE_TARGET inconsistent?
Date: Sat, 07 Jul 2018 19:28:04
Message-Id: 0MTgqe-1fTBhn1HLE-00QSDu@smtp.web.de
In Reply to: Re: [gentoo-user] PYTHON_SINGLE_TARGET inconsistent? by Franz Fellner
1 On Sat, 7 Jul 2018 21:51:31 +0300
2 Franz Fellner <alpine.art.de@×××××.com> wrote:
3
4 > It's not automatically doing magic but using things specified in the
5 > profile. In this case look at ${PORTDIR}/profile/base/package.use
6 > Setting PYTHON_SINGLE_TARGET (which is expanded to those USEFlags) in your
7 > make.conf will shadow those from the profile and spit out an error.
8 >
9 > 2018-07-07 21:45 GMT+03:00 Vadim A. Misbakh-Soloviov <gentoo@×××.name>:
10 >
11 > > The package you're referring to have only support of python2 interpreters
12 > > (python2_7 (CPython) and pypy (not the pypy3)).
13 > >
14 > > It seems, by default (if neither of PYTHON_SINGLE_TARGET is set), portage
15 > > tries to do the "magic" (well, in my opinion, it opposes to the Gentoo
16 > > Philosophy, and it should throw the same error even with "defaults") and
17 > > automatically chooses the 2_7 single target for it.
18 > >
19 > > But when you explicitly specify the targets in make.conf, it obeys and
20 > > don't
21 > > do that magic anymore, so condition of "exactly one of supported
22 > > single_targets (pypy, pyhton2.7)" is not meeting anymore".
23 > >
24 > > That's why you getting the error.
25 > >
26 > > В письме от суббота, 7 июля 2018 г. 21:31:48 MSK пользователь Andreas Fink
27 > > написал:
28 > > > Hello,
29 > > > I have a question considering PYTHON_SINGLE_TARGET because it seems to
30 > > > behave inconsistently on my system and I cannot find any documentation
31 > > > about it, that would guide me in the right direction how to fix it.
32 > > > Running emerge --info I see the following (I'm on ~amd64):
33 > > > ... PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7
34 > > python3_5"
35 > > > ...
36 > > >
37 > > > This output is the default for ~amd64, neither PYTHON_SINGLE_TARGET nor
38 > > > PYTHON_TARGETS has been set explicitly.
39 > > > If I do an emerge -av asciidoc, I see the following output:
40 > > > ebuild R ] app-text/asciidoc-8.6.10::gentoo USE="-examples
41 > > -graphviz
42 > > > -highlight {-test}" PYTHON_SINGLE_TARGET="python2_7 -pypy"
43 > > > PYTHON_TARGETS="python2_7 -pypy"
44 > > >
45 > > > Setting PYTHON_SINGLE_TARGET and PYTHON_TARGETS in /etc/portage/make.conf
46 > > > explicitly to: PYTHON_SINGLE_TARGET="python3_5"
47 > > > PYTHON_TARGETS="python2_7 python3_5"
48 > > >
49 > > > Now emerge --info doesn't show any difference. It's still the same
50 > > output.
51 > > > Doing an emerge -av asciidoc I get now this output:
52 > > > !!! The ebuild selected to satisfy "asciidoc" has unmet requirements.
53 > > > - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight
54 > > > -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-pypy -python2_7"
55 > > > PYTHON_TARGETS="python2_7 -pypy"
56 > > >
57 > > > The following REQUIRED_USE flag constraints are unsatisfied:
58 > > > exactly-one-of ( python_single_target_pypy
59 > > > python_single_target_python2_7 )
60 > > >
61 > > >
62 > > > This seems for me to be really inconsistent, considering the fact that we
63 > > > usually request users to provide an emerge --info, which wouldn't show
64 > > any
65 > > > difference.
66 > > > Why am I able to merge in the first case the package, but in the second
67 > > case
68 > > > I get an error? I really cannot understand where the
69 > > > python_single_target_python2_7 is set in the first case.
70 > > > Anyone who has more insight into that case?
71 > > >
72 > > > Cheers
73 > > > Andreas
74 > >
75 > >
76 > >
77 > >
78 > >
79 > >
80
81 That was the file I was looking for. Thank you :)