Am 17.10.2016 um 14:03 schrieb Vlad K.:
> On 2016-10-17 13:27, Gerhard Schmidt wrote:
>>
>> Please do not break systems without a really good reason. This we can
>> discus in 4 years when support for python2 will end, but not until than.
>
> I agree with the bit of "let's not break systems", but n
Am 17.10.2016 um 13:46 schrieb Ruslan Makhmatkhanov:
> Gerhard Schmidt wrote on 10/17/2016 14:27:
>> Am 17.10.2016 um 12:39 schrieb Ruslan Makhmatkhanov:
>>> Gerhard Schmidt wrote on 10/17/2016 11:07:
Am 16.10.2016 um 21:22 schrieb Ruslan Makhmatkhanov:
> - if port has a build dependency u
On 2016-10-17 13:27, Gerhard Schmidt wrote:
Please do not break systems without a really good reason. This we can
discus in 4 years when support for python2 will end, but not until
than.
I agree with the bit of "let's not break systems", but not with the
second part.
Meanwhile, pkg variant
Gerhard Schmidt wrote on 10/17/2016 14:27:
Am 17.10.2016 um 12:39 schrieb Ruslan Makhmatkhanov:
Gerhard Schmidt wrote on 10/17/2016 11:07:
Am 16.10.2016 um 21:22 schrieb Ruslan Makhmatkhanov:
- if port has a build dependency upon python and it can be built both
with python2 and python3, force
Am 17.10.2016 um 12:39 schrieb Ruslan Makhmatkhanov:
> Gerhard Schmidt wrote on 10/17/2016 11:07:
>> Am 16.10.2016 um 21:22 schrieb Ruslan Makhmatkhanov:
>>> - if port has a build dependency upon python and it can be built both
>>> with python2 and python3, force it to build with python3
>>> - if s
On 2016-10-17 12:35, Ruslan Makhmatkhanov wrote:
What I actually meant is to utilize USES=python:3.3+ for such ports,
to make it pick up default python3 version.
Yeah I "misunderstood you correctly", heh, sorry I wanted to say two
different things at once
The only problem with that (and
Gerhard Schmidt wrote on 10/17/2016 11:07:
Am 16.10.2016 um 21:22 schrieb Ruslan Makhmatkhanov:
- if port has a build dependency upon python and it can be built both
with python2 and python3, force it to build with python3
- if some standalone application can be running both with python2 and
pyt
On Mon, Oct 17, 2016 at 01:35:45PM +0300, Ruslan Makhmatkhanov wrote:
> Ok, PHB was just an example. But it should be some "authoritative" place to
> encourage people to change their ports and to prevent adding of new ports
> without specific python version set (I still see many new ports added wit
Vlad K. wrote on 10/17/2016 13:04:
Hi all!
On 2016-10-17 09:47, Kubilay Kocak wrote:
On 17/10/2016 6:22 AM, Ruslan Makhmatkhanov wrote:
- if port has a build dependency upon python and it can be built
both with python2 and python3, force it to build with python3 - if
some standalone applicat
Hi all!
On 2016-10-17 09:47, Kubilay Kocak wrote:
On 17/10/2016 6:22 AM, Ruslan Makhmatkhanov wrote:
- if port has a build dependency upon python and it can be built
both with python2 and python3, force it to build with python3 - if
some standalone application can be running both with python2
Am 16.10.2016 um 21:22 schrieb Ruslan Makhmatkhanov:
> - if port has a build dependency upon python and it can be built both
> with python2 and python3, force it to build with python3
> - if some standalone application can be running both with python2 and
> python3 and it have equivalent python3 de
On 17/10/2016 6:22 AM, Ruslan Makhmatkhanov wrote:
> Hi,
>
> Python 2.7 will have no upstream support after 2020, and right now it
> no more getting new features. So I'd want to start poisoning^W
> introducing python3 into user system via ports tree and here is what
> I suggest to start to do righ
12 matches
Mail list logo
