changing default perl

Ryan Schmidt ryandesign at
Mon Nov 11 03:06:13 PST 2013

On Nov 5, 2013, at 08:46, Daniel J. Luke wrote:

> I would say we should even go further, and get rid of all of the p5-* ports.
> Instead, we should install perl5 as the latest stable perl, and include our own 'cpanm' program (like how perlbrew has it's own) which would download/build/(test)/install modules (probably into a DESTROOT to allow MacPorts to do the actual install and to take advantage of Macports being able to do unininstall). We could add a new dependency type (and associated functionality) to allow ports to still depend on perl modules, and the perl5 port could uninstall/reinstall all of the installed perl modules when upgraded (or actually, on post-activate). 

If we don’t have a portfile for each CPAN module, how would we:

* not update to a newer available version if that version did not build on OS X?
* apply patches?
* blacklist a compiler?
* add a flag to CFLAGS?
* check the license to check if a dependent is distributable?

It seems like each of these would require special workarounds, which are not needed with the current way of creating a portfile for each package.

More information about the macports-users mailing list