On Feb 5, 2015, at 9:54 PM, Brandon Allbery wrote: > On Thu, Feb 5, 2015 at 10:46 PM, Ryan Schmidt wrote: >> I think the perl5 portgroup is supposed to contain code now to make it easy >> to create perl variants, instead of having to write all this code to do it >> manually. > > eperl is not a Perl module though, it is a Perl *interpreter* (embedded > Perl). The portgroup fits somewhat dubiously as a result, and it's easier to > duplicate that part of the portgroup logic than to suppress or mutate all the > rest of the portgroup's logic.
I thought the perl5 portgroup now has two purposes: 1. to implement subports for perl modules 2. to add perl variants to ports that use perl I was suggesting to use this second new functionality of the perl5 portgroup in the eperl port. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
