| 1 |
Dnia 2015-07-25, o godz. 14:24:27 |
| 2 |
Davide Pesavento <pesa@g.o> napisał(a): |
| 3 |
|
| 4 |
> On Sat, Jul 25, 2015 at 2:03 PM, Michał Górny <mgorny@g.o> wrote: |
| 5 |
> > Dnia 2015-07-25, o godz. 13:37:03 |
| 6 |
> > Davide Pesavento <pesa@g.o> napisał(a): |
| 7 |
> > |
| 8 |
> >> On Sat, Jul 25, 2015 at 12:37 PM, Michał Górny <mgorny@g.o> wrote: |
| 9 |
> >> > While at it, I also added some 'unsupported' wrappers to ban trying to |
| 10 |
> >> > use pythonY (accidental fallback to system python) when pythonX is |
| 11 |
> >> > selected via wrapper, and changed the exit code for unsupp-scripts. |
| 12 |
> >> |
| 13 |
> >> Can you clarify the consequences of this change please? e.g. is it |
| 14 |
> >> still possible to call "naked" python2 from src_prepare() of a package |
| 15 |
> >> using python-r1.eclass, such as dev-python/sip? |
| 16 |
> > |
| 17 |
> > If you call python_setup and ensure python2 is selected beforehand, |
| 18 |
> > yes. Otherwise, you're doing a QA violation and it never were supported. |
| 19 |
> > |
| 20 |
> |
| 21 |
> Funny. I'm pretty sure you suggested the current implementation |
| 22 |
> (directly calling python2) when we first switched to |
| 23 |
> python-r1.eclass... |
| 24 |
|
| 25 |
Nope. I'm pretty sure I never suggested or accepted any kind of direct |
| 26 |
dev-lang/python dependencies or python[23] calls. |
| 27 |
|
| 28 |
-- |
| 29 |
Best regards, |
| 30 |
Michał Górny |
| 31 |
<http://dev.gentoo.org/~mgorny/> |
Archives