[MacPorts] #34570: perl5.16 - new port
Ryan Schmidt
ryandesign at macports.org
Wed May 23 17:14:24 PDT 2012
On May 22, 2012, at 15:12, Bjarne D Mathiesen wrote:
> Ryan Schmidt wrote:
>>
>> On May 22, 2012, at 14:27, Bjarne D Mathiesen wrote:
>>
>>> MacPorts wrote:
>>>> #34570: perl5.16 - new port
>>>> --------------------------------------+-------------------------------------
>>>> Reporter: macintosh@… | Owner: macports-tickets@…
>>>> Type: submission | Status: new
>>>> Priority: Normal | Milestone:
>>>> Component: ports | Version: 2.1.1
>>>> Keywords: | Port: perl5.16
>>>> --------------------------------------+-------------------------------------
>>>>
>>>> Comment(by macintosh@…):
>>>>
>>>> line 42 in _resources/port1.0/group/perl5-1.0.tcl has to be modified to
>>>> :[[BR]]
>>>> {{{default perl5.branches {"5.8 5.10 5.12 5.14 5.16"} }}}
>>>>
>>>
>>> Ought this to be enough to get macports to genereate the subports of the
>>> p5-<something> ports ???
>>>
>>> I can't get it to work / recognise that the subports for p5.16 has to be
>>> generated and recognised :-(
>>
>> Did you rerun "portindex" from the top of your ports tree after doing that?
>
> wasn't aware of that command, but ...
>
> pro17:MacPorts root# portindex
> /macports/var/macports/sources/rsync.macports.org/release/tarballs/ports
> Creating port index in
> /macports/var/macports/sources/rsync.macports.org/release/tarballs/ports
> Adding port databases/mysql51
> Adding subport mysql51-server
> ...
> Adding port www/mod_perl2
> Adding port www/mod_security2
>
> Total number of ports parsed: 28
> Ports successfully parsed: 28
> Ports failed: 0
> Up-to-date ports skipped: 14189
>
> That just adds the ports I have in my local repo without adding the
> p5.16 sub-ports
And you're sure the perl5-1.0.tcl file you're modifying is the one in the directory /macports/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/groups?
If so, then maybe portindex does some kind of mtime checking and only indexes Portfiles newer than the PortIndex files. In that case, try deleting PortIndex and PortIndex.quick before running portindex. If that solves it, then I guess we'll have to manually intervene on the servers too when we do this update.
It seems weird to me that a change in the portgroup should be allowed to create new subports in ports that have not themselves been modified to indicate that that's ok. It seems to me that instead each p5 port should be specifying which perl versions it's compatible with. Thus, when a new version of perl is released, each p5 port would be modified to indicate its compatibility with that new version, thus getting that port's new p5.16 subport into the index at that time. That's at least the approach I'm taking in the new unified php ports.
More information about the macports-dev
mailing list