Date: Mon, 01 Apr 2013 16:14:25 -0500 From: Joshua Isom <jrisom@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: Ports: make fails, if DESTDIR path has spaces Message-ID: <5159F8B1.9010405@gmail.com> In-Reply-To: <CA%2B7WWScRPa%2B%2BN0vT4nG%2BTM=y0m4EPH6%2BK%2BPPbxOMQeZhowNR7w@mail.gmail.com> References: <20130331.133829.093.1@DOMY-PC> <CADLo839abmZYg3agb6UA=EF7t0tNHo7LyKg%2BSSkgG=85EaaYOQ@mail.gmail.com> <20130401.161353.972.1@DOMY-PC> <CADLo83-Qq8H%2BmCEJvAun7WEaFTOkKphy5erXvonrp2TpyOaDUg@mail.gmail.com> <CA%2B7WWScRPa%2B%2BN0vT4nG%2BTM=y0m4EPH6%2BK%2BPPbxOMQeZhowNR7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/1/2013 11:45 AM, Kimmo Paasiala wrote: > On Mon, Apr 1, 2013 at 7:30 PM, Chris Rees <crees@freebsd.org> wrote: >> On 1 April 2013 17:13, <rank1seeker@gmail.com> wrote: >>>> Try "DESTDIR='/usr/TZ\ ONE'; export DESTDIR". >>>> >>>> You need to escape the space. >>> >>> This is '#!/bin/sh' scripting. >>> Doing so "fixes" *.mk, but breaks sh => dir simply doesn't exist anymore. >>> >>> Matthias && Chris => *.mk is at fault here, for not supporting FreeBSD's >>> full range of chars for dir paths >> >> As I explained before, Makefiles and sh have a strange relationship, >> where escaping is similar but different in weird places. >> >> Unless you are an expert, you should not use spaces in pathnames. >> Stop doing it; the ports system is not designed around them. >> > > You could work around the problem by using an external program to do > all the expanding and globbing, it would guarantee that the expansions > are done the same way always and special characters treated in uniform > way. > > -Kimmo Or use a symbolic link to point to the named directory, probably.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5159F8B1.9010405>