1 |
2018-07-26 18:09 GMT+03:00 Mike Gilbert <floppym@g.o>: |
2 |
> On Thu, Jul 26, 2018 at 10:57 AM Grand Duet <grand.duet@×××××.com> wrote: |
3 |
>> |
4 |
>> Just now I have tried to manually set |
5 |
>> |
6 |
>> PYTHON_TARGETS="python2_7 python3_6" |
7 |
>> PYTHON_SINGLE_TARGET="python3_6" |
8 |
>> |
9 |
>> in /etc/portage/make.conf and got the following error: |
10 |
>> |
11 |
>> # emerge --update --deep --with-bdeps=y --newuse --backtrack=120 --ask world |
12 |
>> |
13 |
>> These are the packages that would be merged, in order: |
14 |
>> |
15 |
>> Calculating dependencies... done! |
16 |
>> |
17 |
>> !!! The ebuild selected to satisfy "app-text/asciidoc" has unmet requirements. |
18 |
>> - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight |
19 |
>> -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="(-pypy) -python2_7" |
20 |
>> PYTHON_TARGETS="python2_7 (-pypy)" |
21 |
>> |
22 |
>> The following REQUIRED_USE flag constraints are unsatisfied: |
23 |
>> exactly-one-of ( python_single_target_pypy python_single_target_python2_7 ) |
24 |
>> |
25 |
>> The above constraints are a subset of the following complete expression: |
26 |
>> exactly-one-of ( python_single_target_pypy |
27 |
>> python_single_target_python2_7 ) python_single_target_pypy? ( |
28 |
>> python_targets_pypy ) python_single_target_python2_7? ( |
29 |
>> python_targets_python2_7 ) |
30 |
>> |
31 |
>> (dependency required by "app-text/dvisvgm-2.1.3::gentoo" [installed]) |
32 |
>> (dependency required by "app-text/texlive-2017::gentoo[extra]" [installed]) |
33 |
>> (dependency required by "@selected" [set]) |
34 |
>> (dependency required by "@world" [argument]) |
35 |
>> |
36 |
>> which is similar to those errors I got while trying to set |
37 |
>> |
38 |
>> PYTHON_TARGETS="python2_7 python3_5" |
39 |
>> PYTHON_SINGLE_TARGET="python3_5" |
40 |
>> |
41 |
>> before switching yesterday from python-3.5 to python-3.6 target. |
42 |
>> |
43 |
>> Does it mean that setting python targets in /etc/portage/make.conf is |
44 |
>> not supported any more? |
45 |
> |
46 |
> No, setting PYTHON_TARGETS in make.conf should still work. |
47 |
> |
48 |
> It looks like asciidoc only supports python2, and for some reason |
49 |
> portage is trying to disable python2_7. I'm not sure why that might |
50 |
> be; we enable python2_7 for asciidoc via profiles/base/package.use. |
51 |
> |
52 |
> Have you made some odd change to your profile, or overridden something |
53 |
> in /etc/portage/package.use? |
54 |
|
55 |
No, I have not make any changes in my profile or packege.use. |
56 |
I have only added |
57 |
PYTHON_TARGETS="python2_7 python3_6" |
58 |
PYTHON_SINGLE_TARGET="python3_6" |
59 |
lines to /etc/portage/make.conf |
60 |
|
61 |
And when I comment these two lines in /etc/portage/make.conf, |
62 |
the error mentioned above disappears. |
63 |
|
64 |
Without those two lines in make.conf, I have the following: |
65 |
$ equery uses asciidoc |
66 |
* Found these USE flags for app-text/asciidoc-8.6.10: |
67 |
U I |
68 |
- - examples : Install examples, usually source code |
69 |
- - graphviz : Add support for the Graphviz library |
70 |
- - highlight : Enable source code highlighting |
71 |
+ + python_single_target_python2_7 : Build for Python 2.7 only |
72 |
+ + python_targets_python2_7 : Build with Python 2.7 |
73 |
|
74 |
With those two lines in make.conf, I have the following: |
75 |
$ equery uses asciidoc |
76 |
* Found these USE flags for app-text/asciidoc-8.6.10: |
77 |
U I |
78 |
- - examples : Install examples, usually source code |
79 |
- - graphviz : Add support for the Graphviz library |
80 |
- - highlight : Enable source code highlighting |
81 |
- + python_single_target_python2_7 : Build for Python 2.7 only |
82 |
+ + python_targets_python2_7 : Build with Python 2.7 |
83 |
|
84 |
Ok, got it: the mentioned above settings in /etc/portage/make.conf |
85 |
overrides those of asciidoc. |
86 |
|
87 |
So, the recomendations made in the news "Python 3.6 to become |
88 |
the default target" (mentioned in the thread "Any real need to switch |
89 |
python targets back and forth every month?") on how to set python |
90 |
targets in /etc/portage/make.conf was actually useless. |
91 |
|
92 |
Thank you for all who replied to this thread. |