Recommendations for version numbers in port names

Bradley Giesbrecht pixilla at
Wed Oct 1 14:05:25 PDT 2014

On Oct 1, 2014, at 1:59 PM, Bradley Giesbrecht <pixilla at> wrote:

> On Oct 1, 2014, at 1:10 PM, Lawrence Velázquez <larryv at> wrote:
>> On Sep 16, 2014, at 5:22 PM, Ryan Schmidt <ryandesign at> wrote:
>>> The problem with dots in port names is that so far "port lint" has declared the dot an illegal character in a variant name. This has led the perl5 port for example to adopt variant names like perl5_16 which I've always found a little confusing. It has been nice that under the original naming scheme, one could assume that in many cases the variant name matches the name of the dependency that will be added. If you want to use the python27 port, you use a port's +python27 variant, etc.
>>> Leaving the dot in would remove the ambiguity, as demonstrated by the Perl ports, and "port lint" may be overly cautious in its prohibition of the dot in variant names. Someone should do some tests. Make variants with dots, like "mysql5.1", and see if they work correctly. Can you install the port? Can you upgrade the port? Can you uninstall the port? What if other variants are also selected? If everything works fine we can relax this lint restriction.
>> A cursory glance at port.tcl suggests that periods are acceptable in variant names.
> Lint warnings aside, after adding a mariadb10.0 variant to sphinx I have been able to install, activate and deactivate sphinx with an assortment of variants including mariadb10.0.

Lint warning gone after adding a "." to the regex on variantname:

Bradley Giesbrecht (pixilla)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <>

More information about the macports-dev mailing list