From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Jonas Fonseca <fonseca@diku.dk>, git@vger.kernel.org
Subject: Re: [PATCH] Fix cygwin install issues
Date: Mon, 10 Oct 2005 08:02:56 -0700 [thread overview]
Message-ID: <434A82A0.7060608@zytor.com> (raw)
In-Reply-To: <7vmzlh7n7h.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jonas Fonseca <fonseca@diku.dk> writes:
>
>
>>Support installing to paths including spaces.
>>Remove any old .exe files so ln will succeed.
>>
>
> This is not a complaint but I am just wondering if:
>
>
>>- $(INSTALL) -d -m755 $(DESTDIR)$(bindir)
>>+ $(INSTALL) -d -m755 "$(DESTDIR)$(bindir)"
>
> this is the right way to quote things. I suspect it might be
> the responsibility of the user to quote them if she chooses to
> set bindir or DESTDIR to a funky value, like this:
>
> $ make bindir="'My Documents\Programs'"
I don't think that's the right approach.
$(INSTALL) -d -m755 '$(DESTDIR)$(bindir)'
... at least handles everything except embedded single quotes. Note
that the single quote is not a special character for make.
> Because depending on how funky the values of bindir and DESTDIR
> are, we cannot say double-quote you are giving them is even the
> right quoting (think double-quote itself as part of the name).
>
> The other "$X" change to cmd-renames is a good change (I thought
> I heard HPA talking about that; maybe he sent one to me and I
> dropped it on the floor by mistake, I dunno). Thanks.
If I dropped it on the floor, it was mentally :-/
-hpa
next prev parent reply other threads:[~2005-10-10 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 8:52 [PATCH] Fix cygwin install issues Jonas Fonseca
2005-10-10 9:03 ` Jonas Fonseca
2005-10-10 9:09 ` Junio C Hamano
2005-10-10 9:26 ` [PATCH] git.sh: quote all paths Jonas Fonseca
2005-10-10 9:32 ` Jonas Fonseca
2005-10-10 15:02 ` H. Peter Anvin [this message]
2005-10-10 16:51 ` [PATCH] Fix cygwin install issues Junio C Hamano
2005-10-10 17:09 ` H. Peter Anvin
2005-10-10 20:52 ` Deal with $(bindir) and friends with whitespaces Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=434A82A0.7060608@zytor.com \
--to=hpa@zytor.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).