Linus Torvalds wrote:
On Mon, 11 Jul 2005, Junio C Hamano wrote:
I am not yet convinced "one variable per GNU program" is the
right way to do (I do agree it is a problem and I appreciate
your trying to solving it; an obvious alternative cop-out would
be to fix this in the user's environment, but there might be a
saner solution)
Yes. As you say, if we do this (and I think it's so ugly that I'm not
convinced we want to), it should be done in git-sh-setup-script _once_
instead of editing every single script.
Agreed: I was much happier with my cogito implementation where I just
put it in cg-Xlib. Is git-sh-setup-script appropriate? At first glance
it had a specific purpose and was not included in a large number of files.
Most everything includes git-sh-setup-script anyway by now.
However, what are the features that break the default apple tools anyway?
Maybe we should avoid using them? OSX clearly comes with "cp" and "xargs"
regardless, what are the flags that don't work with their cruddy versions?
xargs -r, cp -l, cp -u, cp -a. Git uses the first 2, cogito uses all 4.
Last night, I couldn't think of alternatives to these, but I obviously
didn't try very hard. xargs -r can probably happen via a temporary file
and cp -u can probably be simulated using rsync.
[ Rant mode on: ..and who the hell is the idiot at Apple who includes the
old crappy BSD stuff? They already use gcc, so it's totally pointless to
have a NIH thing, when the GNU utilities are just _better_. Maybe
somebody can ask Apple to get with the program and not live in the dark
ages any more. ]
It wasn't long ago that the BSD's and Solaris had the same problems. If
only Apple is in the dark ages, shame on them.
Bryan
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
