1 |
Alan McKinnon wrote: |
2 |
> There's an interesting conversation going on over at gentoo-dev about |
3 |
> python-exec. One response I got is worthy of reposting here for anyone |
4 |
> looking at all the python-exec updates and wondering what it's all |
5 |
> about. The responder is mgorny: |
6 |
> |
7 |
>> One set of questions that were never answered and probably do deserve |
8 |
>> some kind of notification: |
9 |
> I can help you with these. However, I don't know on how much of it |
10 |
> a random user cares. |
11 |
> |
12 |
>> 1. What exactly is python-exec anyway? |
13 |
> It's the wrapper script that chooses the proper version of Python |
14 |
> scripts for the currently selected Python version. Say, when you |
15 |
> install 'foomatic' for p2.6, 2.7, 3.2 and 3.3, /usr/bin/foomatic is |
16 |
> linked to python-exec and it determines which one to run. |
17 |
> |
18 |
>> 2. Why are there two, in dev-python/ and dev-lang/ ? |
19 |
> The intent is that the one in dev-python/ was not slotted and the one |
20 |
> in dev-lang/ is. This seems like the only sane way to support both |
21 |
> slots without rewriting all the existing deps (which doesn't seem to |
22 |
> work) or risking breaking the system. |
23 |
> |
24 |
>> 3. One has a version of -10000, which is *highly* unusual, what is that |
25 |
>> exactly? 1 more than -9999? |
26 |
> It is a plain virtual/compat/meta-package. It is a meaningless version |
27 |
> that is supposed to be larger than anything that was earlier in |
28 |
> dev-python/python-exec and it only pulls in dev-lang/python-exec. |
29 |
> |
30 |
>> 4. There is some kind of migration going on between an old and new |
31 |
>> python-exec, but I can't understand it using only standard portage tools. |
32 |
> Yes. The goal is that everything will dep on dev-lang/python-exec:=. |
33 |
> However, we need to somehow keep things that deped on |
34 |
> dev-python/python-exec in the past working. |
35 |
> |
36 |
> |
37 |
> |
38 |
> Posted in the hope some folks might find the answers useful. |
39 |
> |
40 |
> |
41 |
|
42 |
|
43 |
I was doing my weekly update last night and ran into this: |
44 |
|
45 |
[blocks B ] <dev-python/python-exec-10000 |
46 |
("<dev-python/python-exec-10000" is blocking dev-lang/python-exec-2.0, |
47 |
dev-lang/python-exec-0.3.1) |
48 |
|
49 |
and this little snippet: |
50 |
|
51 |
!!! Multiple package instances within a single package slot have been pulled |
52 |
!!! into the dependency graph, resulting in a slot conflict: |
53 |
|
54 |
dev-libs/icu:0 |
55 |
|
56 |
(dev-libs/icu-51.1-r1::gentoo, ebuild scheduled for merge) pulled in by |
57 |
dev-libs/icu:0/51.1= required by (media-libs/raptor-2.0.9::gentoo, |
58 |
installed) |
59 |
dev-libs/icu:0/51.1= required by (sys-apps/gptfdisk-0.8.6::gentoo, |
60 |
installed) |
61 |
>=dev-libs/icu-4.8.1.1:0/51.1= required by |
62 |
(app-office/libreoffice-4.1.2.3::gentoo, installed) |
63 |
dev-libs/icu:0/51.1= required by (media-libs/libcdr-0.0.14::gentoo, |
64 |
installed) |
65 |
dev-libs/icu:0/51.1= required by (app-text/libmspub-0.0.6::gentoo, |
66 |
installed) |
67 |
dev-libs/icu:0/51.1= required by |
68 |
(media-libs/harfbuzz-0.9.12::gentoo, installed) |
69 |
|
70 |
(dev-libs/icu-51.2-r1::gentoo, ebuild scheduled for merge) pulled in by |
71 |
(no parents that aren't satisfied by other packages in this slot) |
72 |
|
73 |
app-text/poppler:0 |
74 |
|
75 |
(app-text/poppler-0.22.5::gentoo, installed) pulled in by |
76 |
>=app-text/poppler-0.16:0/37=[xpdf-headers(+),cxx] required by |
77 |
(app-office/libreoffice-4.1.2.3::gentoo, installed) |
78 |
|
79 |
(app-text/poppler-0.24.3::gentoo, ebuild scheduled for merge) pulled in by |
80 |
(no parents that aren't satisfied by other packages in this slot) |
81 |
|
82 |
It seems icu and popplar is at it again. I have had the chance to |
83 |
unmerge python-exec and then trying to upgrade to see if it fixes the |
84 |
block yet tho. Hopefully I will be able to try that in a little bit. |
85 |
|
86 |
Dale |
87 |
|
88 |
:-) :-) |
89 |
|
90 |
-- |
91 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |