Re: unknown flavor py37

2022-05-26 Thread Daniel Braniss
> On 27 May 2022, at 02:35, Tatsuki Makino wrote: > > Chris wrote on 2022/05/27 06:41: >> On 2022-05-26 14:29, Tatsuki Makino wrote: >>> >>> env BUILD_ALL_PYTHON_FLAVORS=1 make -C /usr/ports/multimedia/openshot >>> FLAVOR=py39 build >> Wouldn't make -DBUILD_ALL_PYTHON_FLAVORS ... get it? >>

Re: unknown flavor py37

2022-05-26 Thread Tatsuki Makino
Chris wrote on 2022/05/27 06:41: > On 2022-05-26 14:29, Tatsuki Makino wrote: >> >> env BUILD_ALL_PYTHON_FLAVORS=1 make -C /usr/ports/multimedia/openshot >> FLAVOR=py39 build > Wouldn't make -DBUILD_ALL_PYTHON_FLAVORS ... get it? > Or add BUILD_ALL_PYTHON_FLAVORS=true to make.conf(5) work? Even if

Re: unknown flavor py37

2022-05-26 Thread Christoph Moench-Tegeder
## Daniel Braniss (da...@cs.huji.ac.il): > but some have 3.6+, and make FLAVOR=37 failes with unknown flavor … In theory you should only handle FLAVOR manually in rather rare cases. Did you read UPDATING entry 20210425 and set DEFAULT_VERSIONS accordingly? Regards, Christoph -- Spare Space

Re: unknown flavor py37

2022-05-26 Thread Chris
On 2022-05-26 14:29, Tatsuki Makino wrote: Daniel Braniss wrote on 2022/05/27 00:23: sorry, my bad, it was make FLAVOR=py37 and the result was ===> py37-psutil-5.9.1 Unknown flavor 'py37', possible flavors: py38. Defining BUILD_ALL_PYTHON_FLAVORS is a way to unlock this restriction. Perhaps

Re: unknown flavor py37

2022-05-26 Thread Tatsuki Makino
Daniel Braniss wrote on 2022/05/27 00:23: > > sorry, my bad, it was make FLAVOR=py37 > and the result was > ===> py37-psutil-5.9.1 Unknown flavor 'py37', possible flavors: py38. > > Defining BUILD_ALL_PYTHON_FLAVORS is a way to unlock this restriction. Perhaps it should be defined in ENV. (I do

FreeBSD ports you maintain which are out of date

2022-05-26 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

Re: unknown flavor py37

2022-05-26 Thread Daniel Braniss
> On 26 May 2022, at 17:42, Dimitry Andric wrote: > > On 26 May 2022, at 16:10, Daniel Braniss wrote: >> >> im using portmaster. >> >> after a resent update to /usr/ports, the default python became 3.8, fine by >> me, but I still want to >> keep 3,7. >> some Makefiles require 3,8+, again no

Re: unknown flavor py37

2022-05-26 Thread Dimitry Andric
On 26 May 2022, at 16:10, Daniel Braniss wrote: > > im using portmaster. > > after a resent update to /usr/ports, the default python became 3.8, fine by > me, but I still want to > keep 3,7. > some Makefiles require 3,8+, again no problem. > but some have 3.6+, and make FLAVOR=37 failes with un

unknown flavor py37

2022-05-26 Thread Daniel Braniss
im using portmaster. after a resent update to /usr/ports, the default python became 3.8, fine by me, but I still want to keep 3,7. some Makefiles require 3,8+, again no problem. but some have 3.6+, and make FLAVOR=37 failes with unknown flavor … any work around? cheers, danny

Deprecation and removal of devel/flang

2022-05-26 Thread Daniel Engberg
Hi, Just trying to reach out to anyone who's interested and might be affected by this, devel/flang in ports is pretty old by now and considered for deprecation in ports including removal. It is still maintained upstream so if you're interested in keeping it and preferably adopt it please use