Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
list-help:	<mailto:cygwin-apps-help AT sourceware DOT cygnus DOT com>
list-post:	<mailto:cygwin-apps AT sourceware DOT cygnus DOT com>
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-apps AT sourceware DOT cygnus DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Mon, 15 May 2000 14:45:55 -0400
To:	cygwin-apps AT sourceware DOT cygnus DOT com
Subject:	Re: [jorg DOT schaible AT db DOT com: Setup and zlib, libpng]
Message-ID:	<20000515144555.B1937@cygnus.com>
Reply-To:	cygwin-apps AT sourceware DOT cygnus DOT com
Mail-Followup-To:	cgf AT cygnus DOT com, cygwin-apps AT sourceware DOT cygnus DOT com
References:	<20000515180818 DOT 16491 DOT qmail AT web110 DOT yahoomail DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.1.12i
In-Reply-To:	<20000515180818.16491.qmail@web110.yahoomail.com>; from earnie_boyd@yahoo.com on Mon, May 15, 2000 at 11:08:18AM -0700

On Mon, May 15, 2000 at 11:08:18AM -0700, Earnie Boyd wrote:
>
>--- DJ Delorie <dj AT delorie DOT com> wrote:
>>>Uhm, CVS comes to mind as an aide in doing this.
>>
>>When we port a package, we don't always have the ability to check
>>something into the original author's CVS repository.  There may not
>>even be a CVS repository.  Ideally, we'd get our patches accepted back
>>into the official sources.
>
>I was thinking of a local Cygnus CVS cygwin-apps repository *not* the
>official source repository.

I'm willing to set this up.  I have always envisioned something like
this, as much as I hate the thought of having two separate development
trees.  I just bit this bullet for cygwin-xfree.

One procedural problem with this is that sourceware is not currently set
up to deal with a huge influx of "developers" who will maintain their
products using cvs.  I sort of wish that we were as automated as
sourceforce seems to be in this respect.

cgf

- Raw text -