On 2012-3-20 06:18 , Ryan Schmidt wrote: > > Are you suggesting that the directory the portfile is in would still be > called "py-foo" and that the portgroup would set name to for example py27-foo > (picking one of the port's supported python versions) instead of py-foo? I > can see how that might be possible with the perl5 and php portgroups since > they use a .setup procedure that sets the name, but the python portgroup > relies on each portfile to set the name, so I'm not sure how that would work.
The python portgroup already sets some other stuff through the magic of option_proc. But see my other email. - Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
