Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 15 Nov 2001 10:05:49 +0000
From: John Marshall <jmarshall AT acm DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: new site for my ports is up
Message-ID: <20011115100549.A1695@kahikatea.pohutukawa.gen.nz>
References: <5314439342 DOT 20011114212805 AT familiehaase DOT de> <3BF2D797 DOT B0481987 AT ece DOT gatech DOT edu> <20011114211942 DOT GB9636 AT redhat DOT com> <1119104841 DOT 20011114224550 AT familiehaase DOT de> <3BF2F6AD DOT 726DB93E AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3BF2F6AD.726DB93E@ece.gatech.edu>; from cwilson@ece.gatech.edu on Wed, Nov 14, 2001 at 05:56:45PM -0500

On Wed, Nov 14, 2001 at 05:56:45PM -0500, Charles Wilson wrote:
> My point was that the off-site versions should install into /usr/local
> (or /opt/ or whatever, just *NOT* /usr).  When you're ready to
> contribute them to the main dist, THEN (and only then) rebuild them to
> install into /usr and upload (to sourceware) as a test release.

Er, can you say why?

Over in RPM land, I have users telling me that they want the
/usr v /usr/local decision to be determined by whether something is
package managed (and thus uninstallable via rpm/setup), rather than
by whether it happens to come from the vendor.

So I get flamed for producing a .rpm that installs to /usr/local, and
am probably going to change to /usr because I think they're right.

Many of my dumb users want to run Cygwin programs from a DOS window.
So if I installed to /usr/local I would need to tell them to add two
directories (C:\Cygwin\bin & C:\Cygwin\usr\local\bin) to their Windows
PATH instead of one, increasing the scope for screwups.

Currently I produce a package for Cygwin setup.exe that installs to
/usr, and I'm about to start getting flamed for that too?  :-)

Having off-site packages install to /usr/local on Cygwin would certainly
show whether they were official or not (cf rpm -qi), but that information
is already pretty much available in /etc/setup/installed.db if off-site
people deliver their package tarballs to setup in a directory other than
"latest" or "contrib".

    John

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/