On Mar 4, 2015, at 11:52 AM, René J.V. Bertin <rjvber...@gmail.com> wrote:
> On a related note: it'd be nice if MacPorts could be a little bit more > proactive in deactiving conflicting ports. Like when installing a subport > that conflicts with one of its siblings. If both are at the same version I > don't see why `port install foo-B` wouldn't cause the automatic deactivation > of port:foo-A as long as foo-A doesn't provide anything others depend upon > that foo-B doesn't provide. Same for say qt5-mac and qt5-mac-devel, which are > interchangeable but cannot be installed at the same time. If I install or > activate the one, the other could be deactivated automatically. Base doesn't have a concept of equivalence. It doesn't know that qt5-mac and qt5-mac-devel are interchangeable. We could implement virtual ports or something like that, but that's a rather larger project. > (just to be sure, if you declare a path: style dependency, the provided path > is recorded in the registry, right?) I don't think so. I think it just records the port (if any) that satisfies the dependency. vq _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
