svn commit: r464842 - head/devel/py-black

David Naylor naylor.b.david at gmail.com
Thu Mar 22 04:20:34 UTC 2018


On Wednesday, 21 March 2018 22:50:19 Mathieu Arnold wrote:
> On Wed, Mar 21, 2018 at 05:28:19PM +0000, Yuri wrote:
> > On 03/20/18 01:12, Mathieu Arnold wrote:
> > > This was not a mistake, it was the correct way to do it.  Using
> > > PY_FLAVOR is more robust because it will always contain the Python
> > > flavor.
> > 
> > Should python ports always use @${PY_FLAVOR} then?
> 
> Maybe, I do not know.  PY_FLAVOR came late in the flavorization process,
> and I did not think much of it at the time.

PY_FLAVOR solves an important problem: how do you specify the flavor of a 
python dependency (especially if the port does not use python flavors, or no 
flavors).  

Technically, if the port uses python flavors then PY_FLAVOR=FLAVOR, but the 
most robust (and consistent way) is to use @${PY_FLAVOR} for dependencies.  

Regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20180322/fa6c9f16/attachment.sig>


More information about the svn-ports-head mailing list