From: Charles Wilson <cwilson@ece.gatech.edu>
To: "Gerrit P. Haase" <cygwin@cygwin.com>
Cc: 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: <3BF2F6AD.726DB93E@ece.gatech.edu> (raw)
In-Reply-To: <1119104841.20011114224550@familiehaase.de>
"Gerrit P. Haase" wrote:
> > Another question: Why a separate site? Why not avoid the confusion and
> > submit the packages to the main release?
>
> Okidoki, every package that gets in the dist will be removed from this site.
> I think I will have to repack all of them, but that is no problem though it
> will last some days.
> Some needs to be rebuilt then too.
>
> BTW, is it possible to introduce a new path like '/opt' e.g. for Apache, or
> should it better go in /usr/apache, /usr/mysql ...?
Having ports/packages "live" on a separate site for a while, until the
ports "settle down" enough for the porter/maintainer to be confident of
them, is okay. I did that for a year or two with cygutils. Eventually,
I migrated the "important" packages over to the new "official" dist.
Some stuff cannot be distributed from the cygwin mirror system, for
legal or political reasons (think cygipc). [BTW, Gerrit, I have NO
problems with you mirroring the cygipc package. Go ahead. But don't try
to submit it for inclusion in the official dist, 'cause it won't be
accepted]
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.
--Chuck
--
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-14 22: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 [this message]
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 ` Charles Wilson
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 ` Robert Collins
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 ` 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 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 ` Robert Collins
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=3BF2F6AD.726DB93E@ece.gatech.edu \
--to=cwilson@ece.gatech.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).