On Tuesday, October 25, 2016 at 11:35:15 PM UTC-7, Emmanuel Charpentier wrote: > > > > Le mercredi 26 octobre 2016 00:42:01 UTC+2, John H Palmieri a écrit : >> >> I have no opinion on whether this approach is on the whole a good idea, >> but I will point out that "which curl" is not as portable as "command -v >> curl". We had an issue a while ago with "which" not behaving properly on >> some platform -- maybe on Solaris "which blah" had a return status of 0 >> even if "blah" was not present? I forget. >> > > Note that we don't use the return status, but the path expansion. I've no > idea about the portability of both ; I note that which is a standard > binary, whereas command is internal to bash. Pick your portability poison... >
I don't even remember if the return status was the issue. I would also point out that according to the web page http://pubs.opengroup.org/onlinepubs/9699919799/, "command" is listed as a standard shell utility, but not "which". -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
