Re: Installation failure caused by CDPATH environment variable

3 messages, 3 authors, 2016-06-15 · open the first message on its own page

Re: Installation failure caused by CDPATH environment variable

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:20

David Kastrup [off-list ref] writes:
Don't educate people.  Just don't trigger their problems.  Of course,
there are millions of ways of shooting oneself in the foot, but in
this case the same foot has been hit several times already.
Yup.  We do exactly that in git-clone, git-sh-setup and
t/test-lib to avoid getting bugged by this stupidity.

Re: Installation failure caused by CDPATH environment variable

From: Wincent Colaiuta <hidden>
Date: 2016-06-15 22:43:20

El 12/7/2007, a las 10:34, Junio C Hamano escribió:
David Kastrup [off-list ref] writes:
quoted
Don't educate people.  Just don't trigger their problems.  Of course,
there are millions of ways of shooting oneself in the foot, but in
this case the same foot has been hit several times already.
Yup.  We do exactly that in git-clone, git-sh-setup and
t/test-lib to avoid getting bugged by this stupidity.
El 12/7/2007, a las 9:51, David Kastrup escribió:
[ "X" = "X$CDPATH" ] || unset CDPATH # ignore braindamaged exports
Whatever decision is taken in the end, I think we should avoid terms  
like "stupidity" and "braindamaged" to avoid causing possible  
offense. Exporting CDPATH is a simple mistake that can be made  
inadvertently or unwittingly, but very easily (Googling for "export  
CDPATH" yields 18,000+ results, many of them purporting to be Bash  
"tutorials").

Cheers,
Wincent

Re: Installation failure caused by CDPATH environment variable

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:43:21

Hi,

On Thu, 12 Jul 2007, Wincent Colaiuta wrote:
El 12/7/2007, a las 10:34, Junio C Hamano escribi?:
quoted
David Kastrup [off-list ref] writes:
quoted
Don't educate people.  Just don't trigger their problems.  Of 
course, there are millions of ways of shooting oneself in the foot, 
but in this case the same foot has been hit several times already.
Yup.  We do exactly that in git-clone, git-sh-setup and t/test-lib to 
avoid getting bugged by this stupidity.
El 12/7/2007, a las 9:51, David Kastrup escribi?:
quoted
[ "X" = "X$CDPATH" ] || unset CDPATH # ignore braindamaged exports
Whatever decision is taken in the end, I think we should avoid terms 
like "stupidity" and "braindamaged" to avoid causing possible offense. 
Exporting CDPATH is a simple mistake that can be made inadvertently or 
unwittingly, but very easily (Googling for "export CDPATH" yields 
18,000+ results, many of them purporting to be Bash "tutorials").
Sorry, my words were indeed to strong.  I apologise.  My only excuse is 
that this crops up ever so often, and it does get slightly annoying.  Of 
course, you did not read all those mails, and so my words were unmerited.  

For an example, see

http://article.gmane.org/gmane.comp.version-control.git/13736/match=cdpath

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help