From: "Jochen Küpper" <jochen@unc.edu>
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: <86g07gw0al.fsf@bock.chem.unc.edu> (raw)
In-Reply-To: <032401c16dd1$5a4bbcf0$0200a8c0@lifelesswks>
On Thu, 15 Nov 2001 23:30:46 +1100 Robert Collins wrote:
Robert> ----- Original Message -----
Robert> From: "John Marshall" <jmarshall@acm.org>
>> Over in RPM land, I have users telling me that they want the
"some users" I hope. Definitely not all:)
>> >> /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.
That's a nice idea...
Robert> Good point.
But I don't think so. After all there is /usr for the vendor,
/usr/local for local stuff, and then there is still /opt and
("sometimes") /usr/local/opt. I think nowadays the best solution is to
put non-vendor non-local stuff into /opt.
And I can live with the current theme that a rpm I download is not
"local". But if it's not from the vendor, it obviousy isn't:)
>> 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.
Well, have you considered /opt?
Robert> I actually don't think that 'off-site' really means much w.r.t. where a
Robert> package installs.
But it does mean soemthing in regard to where I look for that
package. If I nuke all of /usr but /usr/local and then reinstall the
vendor system, I expect my system to work as before (well, beside
config and such).
Greetings,
Jochen
--
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Ãgalité, Fraternité GnuPG key: 44BCCD8E
Sex, drugs and rock-n-roll
--
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 14:56 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
2001-11-11 8:26 ` Robert Collins
2001-11-11 8:26 ` Jochen Küpper [this message]
2001-11-11 8:26 ` Stipe Tolj
2001-11-11 8:26 ` Jochen Küpper
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 ` Charles Wilson
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 ` 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 ` Gerrit P. Haase
2001-11-11 8:26 ` Stipe Tolj
-- strict thread matches above, loose matches on Subject: below --
2001-11-11 8:26 David A. Cobb
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
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=86g07gw0al.fsf@bock.chem.unc.edu \
--to=jochen@unc.edu \
--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).