On Jul 19, 2016, at 10:01 AM, David Evans wrote:

> On 7/19/16 5:41 AM, Ryan Schmidt wrote:
>> 
>>> On Jul 12, 2016, at 7:16 AM, dev...@macports.org wrote:
>>> 
>>> Revision
>>> 150102
>>> Author
>>> dev...@macports.org
>>> Date
>>> 2016-07-12 05:16:16 -0700 (Tue, 12 Jul 2016)
>>> Log Message
>>> 
>>> p5-gearman-server: update to version 1.130.1, homepage, dependencies.
>>> Modified Paths
>>> 
>>>     • trunk/dports/perl/p5-gearman-server/Portfile
>>> Diff
>>> 
>>> Modified: trunk/dports/perl/p5-gearman-server/Portfile (150101 => 150102)
>>> 
>>> --- trunk/dports/perl/p5-gearman-server/Portfile    2016-07-12 12:03:35 UTC 
>>> (rev 150101)
>>> +++ trunk/dports/perl/p5-gearman-server/Portfile    2016-07-12 12:16:16 UTC 
>>> (rev 150102)
>>> 
>>> @@ -5,7 +5,7 @@
>>> PortGroup           perl5 1.0
>>> 
>>> perl5.branches      5.22 5.24
>>> -perl5.setup         Gearman-Server 1.12
>>> +perl5.setup         Gearman-Server v1.130.1
>>> categories          perl net
>>> license             {Artistic-1 GPL}
>>> platforms           darwin
>> 
>> This makes the "v" appear as part of the version number in "port info", 
>> which we don't want:
>> 
>> $ port info p5-gearman-server
>> p5-gearman-server @v1.130.1 (perl, net)
>> Replaced by:          p5.22-gearman-server
>> Sub-ports:            p5.22-gearman-server, p5.24-gearman-server
>> 
>> Description:          Function call router and load balancer
>> Homepage:             http://gearman.org/
>> 
>> Library Dependencies: p5.22-gearman-server
>> Platforms:            darwin
>> License:              Artistic-1 GPL
>> Maintainers:          nomaintainer
>> 
>> 
>> There are a few other perl module ports that use the "v" prefix before their 
>> version number; maybe one of them has a good recipe you can follow to avoid 
>> this problem.
>> 
> 
> Thanks, Ryan.  Fixed in r150468.  I'm surprised that there aren't more of 
> these since the 'version' module which aims to
> normalize perl version numbers always includes the 'v' prefix in the 
> normalized version.

I haven't seen it come up that often, but if it's being recommended somewhere 
and more perl modules are adopting it, maybe the perl5 portgroup should do 
something to help with this situation.


_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to