I currently use the +with_default_names variant, and I do not think removing it will be a good idea. It sounds like from those bugs above, the main problem is just that those names cause issues with installing new ports that expect the names to be the built-in commands. Is there any way that those names could be ignored just for Macports builds?
Since the issues only come up with people who actually use the variant, alternatively you could just put up a big warning saying that there could be problems when people install it. I really like having the +with_default_names variant and would rather not have to make extra changes to my path to accomodate certain particular ports. Thanks, Kris On Fri, Aug 21, 2009 at 2:08 PM, Rainer Müller<[email protected]> wrote: > On 2009-08-21 19:13 , Ryan Schmidt wrote: >> On Aug 21, 2009, at 11:36, Rainer Müller wrote: >>> You would only have to add ${prefix}/gnubin at the front of your >>> PATH to >>> use the GNU versions. >> >> ${prefix}/gnubin would be an mtree violation, which we try to avoid, >> but ${prefix}/libexec/${name} could be reasonable, and has precedent. > > I agree that we should avoid mtree violations. Actually the libexec path > is meant for binaries to be run from other binaries but not by the user. > These GNU tools are meant to be run by the user, so they do not really > fit into libexec in my opinion. > > Rainer > _______________________________________________ > macports-dev mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
