<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Well, on my installation I have:<div class=""><br class=""></div><div class=""><div class="">brew --prefix gnu-getopt</div><div class="">/Users/jlaffaye/homebrew/opt/gnu-getopt</div></div></div></div></div></blockquote><div><br class=""></div><div>Okay, fair enough. Then we should have a fallback.</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">I also want to suggest adding an environment variable to specify the location to not run this discovery step, so people in my situation can avoid calling brew each time they call pass.</div></div></div></blockquote></div><br class=""><div class="">This is a quite good idea. I would suggest to have a <font face="Menlo" class="">ENV</font> variable to the path. If the variable is not set, pass will look up the prefix in two or three default locations, as we currently propose with the for loop. If there is no <font face="Menlo" class="">gnu-getopt</font>, fire up <font face="Menlo" class="">brew —prefix gnu-getopt</font> as a fallback.</div><div class=""><br class=""></div><div class="">Maybe this for loop could also be avoided if the three paths are added to <font face="Menlo" class="">$PATH</font> when the script starts?</div><div class=""><br class=""></div><div class="">I will think about this and post a patch as soon as I am satisfied.</div></body></html>