On 01/01/2015 02:57 PM, Kip Warner wrote: > On Wed, 2014-12-31 at 12:02 -0500, David A. Wheeler wrote: >> They can do workarounds with symlinks, etc., to try to *hide* the reality, but >> since autoconf is supposed to do things *automatically*, that means that >> autoconf fails to do the one job it's supposed to do: automatic configuration. > > Agreed. The whole purpose of autoconf is to help write portable scripts. > Paths with spaces in them, whether we like them or not, is often > uncontrollable and a fact of reality. While paths with spaces in them may be a fact of reality, they are non-portable according to POSIX. It is going to be an uphill battle if you want to submit patches to make autoconf automatically handle file names with spaces, as there is nothing portable about them. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
