sysutils/ansible and FLAVOR (Python 3.6 support)

[Matthew Seaman]

On 15/05/2018 08:02, Christopher Hall wrote:
> Hello everyone,
> 
> I am looking at which is the best way to modify the sysutils/ansible
> port so that it will use Python3.6. Currently it has the "noflavors"
> option in the USE_PYTHON line son only a single packages with
> Python2.7 exists in the pkg repo.
> 
> 
> Should it be renamed to sysutils/py-ansible and "noflavors" removed?
> To produce both py27-ansible and py36-ansible packages in repo,
> allowing a choice of Python version
> 
> Alternatively, is it better to keep the name as sysutils/ansible and
> just change the "USES=python" to "USES=python:3.6+".  However this would
> make it a Python3 only package.
> 
> Any suggestions as to which approach would be preferable?
> 

Having python-3.6 versions of ansible avaialbe in the default package 
repos is a good idea -- it's already easy enough to build-you-own 
ansible packages against python-3.6 and that works fine.  It's also fine 
to use that python-3.6-ized ansible against a host with only python-2.7 
installed.

Take a look at eg. the databases/phpmyadmin port for an example of a 
flavoured port that doesn't have a language dependent (in this case 
php-) prefix.  Just add PKGNAMESUFFIX and take away the noflavors from 
USES, plus add flavour markers to any dependencies that need them.

You'll end up with packages called ansible-py27 and ansible-py36.

	Cheers,

	Matthew