On Fri, Sep 18, 2009 at 1:04 AM, Blair Zajac <[email protected]> wrote:
> But if I want the port, I want the port. What's the point of installing it > if you don't want it as the default. > That doesn't particularly make any sense. I can install python26 and python31, but I still want python26 to be the default, but be able to use python31 if I want to. As for building ports, then we set the port to use /usr/bin/sed and not > $prefix/bin/sed for the few cases that are different. > Right, and for the thousands and thousands of lines of Makefiles for the many packages that either ignore documented ./configure variables, use them in some places but not in others, fetches the needed utility out of your $PATH of the executing shell, or are hardcoded, not to mention the large amount of portfiles and patches that would need to be modified...no, that idea makes no sense whatsoever. I understand what you're trying to say, but I don't think you realize the vast ramifications of it. > Blair > > > On Sep 17, 2009, at 11:02 PM, Mark A. Miller wrote: > > Exactly, some packages that are set up to build nicely on MacOSX expect >> BSD tools, not GNU. Good example that has bitten me many times, is GNU's >> "sed -r" versus BSD's "sed -E". Et cetera. >> >> On Fri, Sep 18, 2009 at 12:56 AM, Jeremy Lavergne < >> [email protected]> wrote: >> GNU utilities versus BSD utilities ... they don't do the same thing in the >> same way. >> >> This results in some stuff breaking. >> >> >> On Sep 18, 2009, at 1:54 AM, Blair Zajac wrote: >> >> Are there any reasons not to do this? >> >> >> >> >> -- >> Mark A. Miller >> [email protected] >> > > -- Mark A. Miller [email protected]
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
