Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Thu, 18 Nov 1999 19:51:23 -0500
Message-Id: <199911190051.TAA11591@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <38348E7A.F5622E72@vinschen.de> (message from Corinna Vinschen on
	Fri, 19 Nov 1999 00:40:42 +0100)
Subject: Re: Maintainers wanted
References: <19991118160433 DOT A13395 AT cygnus DOT com> <199911182222 DOT QAA18587 AT mercury DOT xraylith DOT wisc DOT edu> <19991118173002 DOT B14542 AT cygnus DOT com> <38348E7A DOT F5622E72 AT vinschen DOT de>


> Is it needful to create another server with ported software?

Good question.  The answer depends on a lot of things, but I can see a
couple of ways this could work:

* sourceware contains the same packages as in b20.1, but broken into
  separate packages.  Franken.de continues to carry what it does.

* sourceware takes over the job franken.de had, acting as a central
  repository for all ports.

* Franken.de mirrors from sourceware so that both are available.

* sourceware mirrors from franken.de (and/or other sites) to act as a
  "collector" of ports.

Personally, I like the second option, but *only* if the process for
uploading ports (and the rules about uploading) are easy to understand
and follow.  If we had one central site, we could organize the mirrors
better and offer more access to the software, but if it's difficult
for the maintainers to put stuff in it, it just won't work.

If sourceware did become the central repository, I would argue for
keeping full sources for each package on it, not just patches.