Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <032401c16dd1$5a4bbcf0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "John Marshall" <jmarshall@acm.org>, <cygwin@cygwin.com>
References: <5314439342.20011114212805@familiehaase.de> <3BF2D797.B0481987@ece.gatech.edu> <20011114211942.GB9636@redhat.com> <1119104841.20011114224550@familiehaase.de> <3BF2F6AD.726DB93E@ece.gatech.edu> <20011115100549.A1695@kahikatea.pohutukawa.gen.nz>
Subject: Re: new site for my ports is up
Date: Thu, 15 Nov 2001 23:30:46 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "John Marshall" <jmarshall@acm.org>

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

Good point.

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

This is an orthogonal issue IMO. Cygwin is not installed correctly if
usr\local\bin is not in the path.

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

Nope, because your package was for testing pre-setup moratorium being
lifted, and it's lifted. Your (curl IIRC) package should now get into
setup.exe quite happily.

> 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".

I actually don't think that 'off-site' really means much w.r.t. where a
package installs. By that I mean, does an end user *care* that the
packages came from a given mirror, or that they are available. If we
want'd to only display *official* packages, we could do something based
on the MD5 sums in setup.ini.

Rob


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