From: John Marshall <jmarshall@acm.org>
To: cygwin@cygwin.com
Subject: Re: new site for my ports is up
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <20011115100549.A1695@kahikatea.pohutukawa.gen.nz> (raw)
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/
next prev parent reply other threads:[~2001-11-15 10:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 8:26 Gerrit P. Haase
2001-11-11 8:26 ` Charles Wilson
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Gerrit P. Haase
2001-11-11 8:26 ` Charles Wilson
2001-11-11 8:26 ` Stipe Tolj
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Stipe Tolj
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` John Marshall [this message]
2001-11-11 8:26 ` Charles Wilson
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Charles Wilson
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Jochen Küpper
2001-11-11 8:26 ` Stipe Tolj
2001-11-11 8:26 ` Jochen Küpper
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Stipe Tolj
2001-11-11 8:26 ` Gerrit P. Haase
2001-11-11 8:26 ` Stipe Tolj
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Stipe Tolj
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 Robert Collins
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Charles Wilson
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 David A. Cobb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011115100549.A1695@kahikatea.pohutukawa.gen.nz \
--to=jmarshall@acm.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).