Thread (3 messages) flat view 3 messages, 2 authors, 2016-06-15

Re: [PATCH] perl/Makefile: handle paths with spaces in the NO_PERL_MAKEMAKER section

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:45:07

Possibly related (same subject, not in this thread)

Brandon Casey [off-list ref] writes:
Junio C Hamano wrote:
quoted
Brandon Casey [off-list ref] writes:
quoted
Use double quotes to protect against paths which may contain spaces.
...
+	echo '	mkdir -p "$(instdir_SQ)"' >> $@
Is this sufficient?  We seem to apply double-sq when writing shell
scriptlet in GIT-BUILD-OPTIONS from the main Makefile, and I suspect you
would need to do something similar.
It seems to be sufficient. The double quotes survived into my perl.mak file
and the two perl modules were installed correctly when I supplied a prefix
with spaces. Is there something else to be concerned about?
I think the generic way GIT-BUILD-OPTIONS writing is done covers cases
where the installation directory has funnies other than whitespace, e.g. 
double quotes.  Is your 'echo "$(instdir_SQ)"' sufficient?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help