Message-ID: <4A185B72.1000408@gmail.com>
Date: Sat, 23 May 2009 21:24:18 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Static linking issue under cygwin.
References: <4f8dccd00905231221v2f82acb9rcf1ffa9f228650be@mail.gmail.com> 	 <4A184ED3.70504@aol.com> <4f8dccd00905231302kbcd4bd2v4111e3492824db13@mail.gmail.com>
In-Reply-To: <4f8dccd00905231302kbcd4bd2v4111e3492824db13@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Vladimir A. Petrov wrote:
> By the way
> why "Program Files" directory is worse than others if it easily can be
> accessed by the fully qualified path? Try to say that it is strange
> enough to the PostgreSQL guys, they are decided to put their libs
> there, not I, I've just used default installetion paths. :-)

  There's nothing *intrinsically* worse about it, it's just a directory path
like any other... except not quite like any other, because (on Linux anyway)
it's actually pretty rare to have a space in a directory path, and lots and
lots of scripts and utilities fall down badly when they try dealing with paths
with embedded spaces because they subject them to unquoted shell handling,
which treats the space as a word-separator.  So, it's not "worse", but it is
"unusual and therefore less well tested and therefore more prone to bugs".

    cheers,
      DaveK


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/