1 |
Currently, we're passing build-dir and stuff implicitly in esetup.py. |
2 |
We're appending the 'build' and 'egg-info' commands which is confusing |
3 |
and not always requested. |
4 |
|
5 |
These patches use different approach for setting build-dir. We create |
6 |
a per-implementation $HOME, and create .pydistutils.cfg there. This way, |
7 |
we can set all the build-dirs without explicitly invoking any of |
8 |
the commands. |
9 |
|
10 |
Notes: |
11 |
|
12 |
1. esetup.py no longer explicitly invokes 'build' and 'egg-info' -- can |
13 |
be used more widely. |
14 |
|
15 |
2. if esetup.py is called before python_compile(), it doesn't have |
16 |
build-dir set yet. AFAICS this is not an issue but still worth noticing. |
17 |
|
18 |
3. if some ebuild relied on 'esetup.py' implicitly appending 'build' |
19 |
command, it needs to be fixed :). |
20 |
|
21 |
4. implicit 'build' caused implicit rebuild in python_install() for |
22 |
a few packages. That should be fixed now. |
23 |
|
24 |
5. if some package overrides build dirs in setup.cfg, it will override |
25 |
our setting. We need to see if that's a case somewhere and if it causes |
26 |
trouble. |
27 |
|
28 |
That's all I can think of. What do you think? |
29 |
|
30 |
-- |
31 |
Best regards, |
32 |
Michał Górny |