Proposal: default to concurrent

John W. O'Brien john at saltant.com
Tue Jan 31 14:47:15 UTC 2017


Hi Nikolai,

On 1/29/17 23:18, Nikolai Lifanov wrote:
> I think the biggest controversy is that binary names are suffixed, which
> may not be what upstream projects like and/or document.
> It may be confusing to users as well.
> 
> If we can get rid of the suffix for PYTHON_CONCURRENT_INSTALL for
> whichever version is PYTHON_DEFAULT, it should be a net positive to
> treat it the same way we did USE_GCC in the past (enable
> PYTHON_NO_CONCURRENT or something and remove it on per-port basis once
> fixed).

The way you describe it makes me think I'm missing something. The way
concurrent works right now, the default version of python gets a script
with no suffix, so there's no suffix to get rid of.

Are there cases where the presence of suffixed binaries conflicts with
upstream and/or causes confusion to users, provided that binaries (or at
least symlinks to them) are also present?

-J

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-python/attachments/20170131/af2cedb0/attachment.sig>


More information about the freebsd-python mailing list