|
From: | Peter Johansson |
Subject: | Re: problem with MKDIR_P defined as relative path to install-sh |
Date: | Fri, 01 Mar 2013 09:40:51 +1000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130108 Thunderbird/10.0.12 |
Hi Eric and Paul, On 03/01/2013 03:08 AM, Eric Blake wrote:
On 02/28/2013 09:57 AM, Paul Eggert wrote:On 02/28/13 05:31, Peter Johansson wrote:would it make sense to defined MKDIR_P with absolute path insteadYes, that sounds reasonable, if someone could prepare a patch along those lines.One wrinkle - absolute paths might contain spaces, whereas relative paths do not, if a package is built in a containing directory named with a space. Does switching to an absolute path risk a problem with proper quoting?
Yes, probably. Automake defines e.g.AUTOCONF = ${SHELL} /home/peterJo/projects/software/yat/build-aux/missing autoconf
and when the path to 'missing' contains a space, it gets quotedAUTOCONF = ${SHELL} "/home/peterJo/projects/software/yat space/autotools/missing" autoconf.
One could, iow, probably borrow some code from Automake. I'll have a look at it but can't promise anything.
Cheers, Peter
[Prev in Thread] | Current Thread | [Next in Thread] |