Ryan Schmidt wrote: > A port can override any phase, but there's little reason to override > fetch and extract, and no reason to override checksum, install, and > activate. That leaves patch, configure, build, and destroot, which is > where ports typically do their distinctive work. muniversal overrides > the default behavior of configure, build, and destroot, so that each > phase iterates over each architecture.
See also what we discussed earlier about the muniversal integration: http://lists.macosforge.org/pipermail/macports-dev/2009-April/008205.html Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
