Message-ID: <43D52030.8020408@verysmall.org>
Date: Mon, 23 Jan 2006 19:28:00 +0100
From: "pobox@verysmall.org" <pobox@verysmall.org>
User-Agent: Thunderbird 1.6a1 (Windows/20060119)
MIME-Version: 1.0
To: cygwin@cygwin.com, ebb9@byu.net
Subject: Re: installation location of packages
References: <43D3F587.3070600@verysmall.org> <43D4DC41.2050308@byu.net>
In-Reply-To: <43D4DC41.2050308@byu.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
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

Eric Blake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> According to pobox@verysmall.org on 1/22/2006 2:13 PM:
>> It seems to me that the cygwin packages are installed in different
>> locations than the locations they would go if ./compile make make
>> install are performed on the source.
> 
> Yes, many packages default to an installation prefix of /usr/local if no
> options were given to ./configure, while cygwin packages intentionally
> override this with ./configure --prefix=/usr.  This distinction is
> recommended by the FHS (http://www.pathname.com/fhs/) so that you can
> compile local updates of your favorite programs to /usr/local/bin without
> overwriting the shipped system programs in /usr/bin.  But if you use
> setup.exe to grab the sources, every one of those src tarballs should come
> with directions (and usually with a script) that tells you exactly which
> options were passed to ./configure when building the official cygwin
> release of that package.

Thanks a lot for the clarification!

Iv.


--
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/