1 |
There's an interesting conversation going on over at gentoo-dev about |
2 |
python-exec. One response I got is worthy of reposting here for anyone |
3 |
looking at all the python-exec updates and wondering what it's all |
4 |
about. The responder is mgorny: |
5 |
|
6 |
> One set of questions that were never answered and probably do deserve |
7 |
> some kind of notification: |
8 |
|
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 |
|
14 |
It's the wrapper script that chooses the proper version of Python |
15 |
scripts for the currently selected Python version. Say, when you |
16 |
install 'foomatic' for p2.6, 2.7, 3.2 and 3.3, /usr/bin/foomatic is |
17 |
linked to python-exec and it determines which one to run. |
18 |
|
19 |
> 2. Why are there two, in dev-python/ and dev-lang/ ? |
20 |
|
21 |
The intent is that the one in dev-python/ was not slotted and the one |
22 |
in dev-lang/ is. This seems like the only sane way to support both |
23 |
slots without rewriting all the existing deps (which doesn't seem to |
24 |
work) or risking breaking the system. |
25 |
|
26 |
> 3. One has a version of -10000, which is *highly* unusual, what is that |
27 |
> exactly? 1 more than -9999? |
28 |
|
29 |
It is a plain virtual/compat/meta-package. It is a meaningless version |
30 |
that is supposed to be larger than anything that was earlier in |
31 |
dev-python/python-exec and it only pulls in dev-lang/python-exec. |
32 |
|
33 |
> 4. There is some kind of migration going on between an old and new |
34 |
> python-exec, but I can't understand it using only standard portage tools. |
35 |
|
36 |
Yes. The goal is that everything will dep on dev-lang/python-exec:=. |
37 |
However, we need to somehow keep things that deped on |
38 |
dev-python/python-exec in the past working. |
39 |
|
40 |
|
41 |
|
42 |
Posted in the hope some folks might find the answers useful. |
43 |
|
44 |
|
45 |
-- |
46 |
Alan McKinnon |
47 |
alan.mckinnon@×××××.com |