On 6/23/15 4:53 PM, Brandon Allbery wrote: > On Tue, Jun 23, 2015 at 4:30 PM, Christopher David Ramos > <[email protected] <mailto:[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. > > -- > brandon s allbery kf8nh sine nomine associates > [email protected] <mailto:[email protected]> > [email protected] <mailto:[email protected]> > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net > > > _______________________________________________ > macports-users mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-users >
Please forgive me if what I'm suggesting is not feasible. That said, it was my understanding that makefiles include instructions on what and where libraries should be built. If there were a special Macports version of git that included a daemon, could it not be used to overrule the default install directories for any libraries a git project's makefile may call for? -- Chris David Ramos GS/P d- s+: a C U* W++ M+ PS++ PE PGP++ t+ !tv b+ G e+++>++++ r _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
