Opened 11 years ago
Closed 11 years ago
#43727 closed defect (wontfix)
perl5 1.0 portgroup cannot handle version numbers with characters
Reported by: | mf2k (Frank Schima) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | ||
Port: |
Description
The perl5 1.0 portgroup has a bug where it cannot handle a version number with non-numeric characters in it. See the p5-sgmlspm port as an example. The version it produced was:
p5.16-sgmlspm @1.3.{}_0 (active)
The issue exists in proc perl5_convert_version
.
Attachments (1)
Change History (6)
comment:1 follow-up: 2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 11 years ago by danielluke (Daniel J. Luke)
Replying to ryandesign@…:
I guess the reason for this is that perl module version numbers are not supposed to have non-numeric characters in them. The author of the affected perl module should be advised of this.
Looks like the last update to that module on CPAN is from 1995, so it seems unlikely that it will get updated/fixed.
Changed 11 years ago by pixilla (Bradley Giesbrecht)
Attachment: | patch-port-group-per5-version-chars.diff added |
---|
comment:3 Changed 11 years ago by pixilla (Bradley Giesbrecht)
I wrote this patch a while back, seems to work ok.
$ port -q installed p5.16-sgmlspm p5.16-sgmlspm @1.30.0ii_1 (active)
comment:4 Changed 11 years ago by mf2k (Frank Schima)
Unfortunately, I do not think that version number is correct for p5-sgmlspm. According to that port's homepage, the version is "1.03ii". In the p5-sgmlspm Portfile, I manually set it to "1.03ii.0".
comment:5 Changed 11 years ago by jmroot (Joshua Root)
Component: | base → ports |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Yeah, this isn’t really a bug, the version number is invalid. Perl rejects it:
% perl -Mversion -e 'print version->parse("1.03ii")->normal' Invalid version format (non-numeric data) at -e line 1.
I’d suggest just setting your own version in such cases.
I guess the reason for this is that perl module version numbers are not supposed to have non-numeric characters in them. The author of the affected perl module should be advised of this.