1 |
Le 21 août 2014 à 15:20, Michał Górny <mgorny@g.o> a écrit : |
2 |
|
3 |
> Use generated setup.cfg file to propagate install paths rather than |
4 |
> passing them via command-line arguments whenever possible, making it |
5 |
> possible to call special install commands without forcing the main |
6 |
> 'install' command. |
7 |
> |
8 |
> For example, if setup.py defines install_doc command that reuses prefix |
9 |
> from install, to use it you'd have to call either: |
10 |
> |
11 |
> esetup.py install --root="${D}" install_doc |
12 |
> |
13 |
> or: |
14 |
> |
15 |
> distutils-r1_python_install install_doc |
16 |
> |
17 |
> both of them forcing (re-)install of the whole package implicitly. |
18 |
> |
19 |
> Instead, we can reuse the setup.cfg file that was added specifically to |
20 |
> solve a similar issue with build paths. Put the default root, byte- |
21 |
> compilation options and script path (if applicable) there. |
22 |
> distutils-r1_python_install still carries --root override for |
23 |
> intermediate root install though. |
24 |
> |
25 |
> Thanks to this, you can run the fore-mentioned command like this: |
26 |
> |
27 |
> esetup.py install_doc |
28 |
> --- |
29 |
|
30 |
Looks great. |
31 |
|
32 |
-- |
33 |
Gilles Dartiguelongue <eva@g.o> |