1 |
Hello, |
2 |
|
3 |
As a result of late doc writing and adding MERGE_TYPE check to |
4 |
python-any-r1_pkg_setup, I'm thinking about adding a new function. |
5 |
|
6 |
The function would, depending on the eclass in use: |
7 |
|
8 |
1. for python-any-r1, be the 'original' version of |
9 |
python-any-r1_pkg_setup, that is finding and setting up the Python |
10 |
version without the MERGE_TYPE check, |
11 |
|
12 |
2. for python-single-r1, be equivalent to python-single-r1_pkg_setup, |
13 |
|
14 |
3. for python-r1, call python_export_best + python_wrapper_setup. |
15 |
|
16 |
So in any of the eclasses, the function would result in Python being |
17 |
set up properly for use in global scope. |
18 |
|
19 |
The question is: how to name the function? We need a name that would be |
20 |
easy to remember and not confusing at the same time. Especially, I'd |
21 |
like to avoid wrongly suggesting that python-r1 needs it -- since it |
22 |
usually doesn't :). |
23 |
|
24 |
-- |
25 |
Best regards, |
26 |
Michał Górny |