sqlgrey: absence of required perl variant, depending on variant of perl5

[ryandesign (Ryan Carsten Schmidt)]

If perl5 is installed with the +perl5_12 variant, sqlgrey fails to be added to the portindex, and cannot be used:

/Volumes/Data/macports/dports/mail/sqlgrey rschmidt$ port info
Error: sqlgrey requires one of these variants: perl5_16 perl5_18 perl5_20
Can't map the URL 'file://.' to a port description file ("absence of required perl variant").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.

[anddam (Andrea D'Amore)]

Cc Me!

[nava@…]

Cc Me!

[marc@…]

Cc Me!

[larryv (Lawrence Velázquez)]

Replying to nava@…:

Cc Me!

You need to actually click the “Cc” button to be Cc’d on a ticket.

[pixilla (Bradley Giesbrecht)]

The sqlgrey port does not have a +perl5_12 variant.

port variants sqlgrey      
sqlgrey has the variants:
[+]mysql: Add mysql driver support
[+]perl5_16: Use MacPorts perl5.16
     * conflicts with perl5_18 perl5_20
   perl5_18: Use MacPorts perl5.18
     * conflicts with perl5_16 perl5_20
   perl5_20: Use MacPorts perl5.20
     * conflicts with perl5_16 perl5_18
   postgresql: Add postgres driver support
   sqlite: Add sqlite driver support
   table_names: Make table names configurable

It would be easy to add a +perl5_12 variant but it is my understanding that "perl<5.16 " is being retired from MacPorts. Openmaintainer welcomes "perl<5.16 ".

[danielluke (Daniel J. Luke)]

Replying to pixilla@…:

It would be easy to add a +perl5_12 variant but it is my understanding that "perl<5.16 " is being retired from MacPorts. Openmaintainer welcomes "perl<5.16 ".

sure, but the port should end up in the index regardless of what port(s) are installed or not - it shouldn't depend on the status of the perl5 port.

[pixilla (Bradley Giesbrecht)]

The perl5 port group starts with this:

options perl5.default_branch perl5.branches
default perl5.default_branch {[perl5_get_default_branch]}

I understood that default option values enclosed in curly-braces were evaluated at first use and only if not already set. Why does it appear that portindex behaves differently?

In the Portfile if I set perl5.default_branch before adding the perl5 port group portindex completes. Can someone suggest a better solution then requiring the setting of perl5.default_branch before including the port group?

[danielluke (Daniel J. Luke)]

Maybe it's a bug in the portgroup?

In any event - the port should be able to be in the index / be processed no matter what ports are installed or aren't installed. I haven't had time to dig into exactly where this isn't working correctly. It's one of the (many) things that we should just resolve by having only one perl.

[pixilla (Bradley Giesbrecht)]

See r127117