On 2012-5-24 10:14 , Ryan Schmidt wrote: > > 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.
Yes, perl5.branches should be specified in each portfile, especially since there are probably modules that don't work with all the perl versions. - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
