> On Jun 23, 2015, at 2:09 PM, Jeremy Lavergne <[email protected]> > wrote: > > On Tue, June 23, 2015 16:53, Brandon Allbery wrote: >> On Tue, Jun 23, 2015 at 4:30 PM, Christopher David Ramos < >> [email protected]> wrote: >> >>> Still, I think the Macports version of git should have >>> some mechanism, or some warning -- something -- to warn or prevent >>> conflicts between Macports and git projects. >>> >> >> Umm, AI much? >> >> >> Basically you seem to be asking for something that can magically analyze >> random source code and determine that it will conflict. This is not as >> simple as you seem to think it is; in fact it's a very unsolved problem. > > Even MacPorts doens't know which of its ports will cause a conflict; it > relies solely on the package maintainers to manually declare them as much. > > If only we tracked what each package installed: we could find all > conflicts before they happen, and we could tell people what packages to > install for a given binary!
+1 — Brad _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
