Hi Yuval,
Yuval Turgeman writes:
> Thanks for the feedback ! What you described is what we are doing
> today, it does the job nicely, I just thought it would be nice to
> avoid 2 calls. Honestly, both VPATH and my patch feel a little hackish
> to me, and the existing way is not really that painf
Hi,
Thanks for the feedback ! What you described is what we are doing today,
it does the job nicely, I just thought it would be nice to avoid 2 calls.
Honestly, both VPATH and my patch feel a little hackish to me, and the
existing way is not really that painful, I guess. Your call, I will not be
Yuval Turgeman writes:
> Because when I want to package an rpm, I have a single %build and
> %install in my spec, so my second call to configure will override the
> first, and then i will need to run make install. So the process would
> be result in something like
>
> (from %build)
> configure PY
Because when I want to package an rpm, I have a single %build and %install
in my spec, so my second call to configure will override the first, and
then i will need to run make install. So the process would be result in
something like
(from %build)
configure PYTHON=/usr/bin/python2
make
configure
Hello,
Yuval Turgeman writes:
> On Tue, Jan 30, 2018 at 2:22 PM, Sandro Bonazzola
> wrote:
>
>> 2018-01-30 11:26 GMT+01:00 Yuval Turgeman :
>>
>>> I added 2 macros (AM_PATH_PYTHON2 and AM_PATH_PYTHON3) to support both
>>> python2 and python3 on the same system. It works in the same way that
>>
2018-01-30 11:26 GMT+01:00 Yuval Turgeman :
> Hi,
>
> I added 2 macros (AM_PATH_PYTHON2 and AM_PATH_PYTHON3) to support both
> python2 and python3 on the same system. It works in the same way that
> AM_PATH_PYTHON works (just a small wrapper around it). Please notice that
> AM_PATH_PYTHON and AM
On Tue, Jan 30, 2018 at 2:22 PM, Sandro Bonazzola
wrote:
>
>
> 2018-01-30 11:26 GMT+01:00 Yuval Turgeman :
>
>> Hi,
>>
>> I added 2 macros (AM_PATH_PYTHON2 and AM_PATH_PYTHON3) to support both
>> python2 and python3 on the same system. It works in the same way that
>> AM_PATH_PYTHON works (just
Hi,
I added 2 macros (AM_PATH_PYTHON2 and AM_PATH_PYTHON3) to support both
python2 and python3 on the same system. It works in the same way that
AM_PATH_PYTHON works (just a small wrapper around it). Please notice that
AM_PATH_PYTHON and AM_PATH_PYTHONx can't be called together.
The motive for
