On Jun 23, 2012, at 4:30 PM, Ryan Schmidt wrote: > On Jun 22, 2012, at 08:30, Daniel J. Luke wrote: >> Either way, the perl5 portgroup takes care of it for most modules, and >> anything that doesn't use it will have to take care of it itself (probably >> by copying code from the perl5 portgroup). > > Except that the code the perl5 portgroup uses relies on variables defined by > the perl5 portgroup and so has to be modified for use in ports not using the > perl5 portgroup. :/
Maybe it makes sense to pull that code out into its own portgroup (that the perl5 portgroup can use)? -- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
