Archives
Archives
| From: | Mike Gilbert <floppym@g.o> | ||
|---|---|---|---|
| To: | "Michał Górny" <mgorny@g.o> | ||
| Cc: | gentoo-python <gentoo-python@l.g.o> | ||
| Subject: | Re: [gentoo-python] [PATCH] Introduce python_setup() as a common name for Python setup function. | ||
| Date: | Sun, 20 Oct 2013 14:53:40 | ||
| Message-Id: | CAJ0EP42z-kCFEMytWOSJ032yAnwrv6sx1zCiqOh1eJVDjves4g@mail.gmail.com | ||
| In Reply to: | [gentoo-python] [PATCH] Introduce python_setup() as a common name for Python setup function. by "Michał Górny" |
||
| 1 | On Sun, Oct 20, 2013 at 3:36 AM, Michał Górny <mgorny@g.o> wrote: |
| 2 | > As described in the ml, the new function does: |
| 3 | > |
| 4 | > * in python-any-r1, choose and set up the best installed impl, |
| 5 | > |
| 6 | > * in python-single-r1, read PYTHON_SINGLE_TARGET and set it up, |
| 7 | > |
| 8 | > * in python-r1, call python_export_best + python_wrapper_setup. |
| 9 | > |
| 10 | > In other words, it's a common way of getting Python build environment |
| 11 | > set up in the ebuild scope. |
| 12 | |
| 13 | Invoking python_setup from pkg_setup in any eclass seems sub-optimal; |
| 14 | especially so in python-any-r1. However, I realize there isn't a great |
| 15 | place to put it. |
| 16 | |
| 17 | Looks ok to me. |
| Subject | Author |
|---|---|
| Re: [gentoo-python] [PATCH] Introduce python_setup() as a common name for Python setup function. | "Michał Górny" <mgorny@g.o> |