On 2013-01-10 15:23, Rainer Müller wrote: > Some other ports using the perl5 port group outside of perl/p5-* suffer > from the same problem: > > $ port -q installed perl5 > perl5 @5.12.4_0+perl5_16 (active) > $ port -q info --depends_lib ikiwiki > port:perl5.16, port:p5.12-cgi-formbuilder, port:p5.12-cgi-session, [...] > $ port -q info --depends_lib psh > port:perl5.16, port:p5.12-term-readline-gnu, port:p5.12-bsd-resource > > The port group is even mixing the versions 5.16 and 5.12 here.
I found another problem like this with the port svk, which appears to be using perl5.16 on my system, but the pre-compiled archive from the buildbot is compiled for perl5.12. $ port -q info --depends_lib svk port:perl5.16, port:p5.16-data-hierarchy, port:p5.16-algorithm-diff, port:p5.16-algorithm-annotate, ... $ port -q contents svk /opt/local/bin/svk-5.12 /opt/local/lib/perl5/vendor_perl/5.12.4/SVK.pm /opt/local/lib/perl5/vendor_perl/5.12.4/SVK/Accessor.pm /opt/local/lib/perl5/vendor_perl/5.12.4/SVK/Command.pm ... This means the behavior of the perl5 port group is effectively broken. If this does not get fixed, no binary archives should be distributed for any port using this port group in its current form, as the build results are not reproducible. Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
