On Sun, Jan 19, 2014 at 11:37 PM, Ryan Schmidt <[email protected]> wrote:
> This situation does not call for the deactivate hack; rather, it calls for > the conflicts_build portgroup. (The port would declare a build conflict with > itself.) But that would lead to the build failing without manual intervention, i.e. manually deactivating the port. I'm trying to automate this so users don't notice the problem. Cheers Adam _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
