Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <396BF256.DB96E24E@ece.gatech.edu>
Date: Wed, 12 Jul 2000 00:21:42 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Valerio Aimale <valerio DOT aimale AT biosgroup DOT com>
CC: cygwin AT sources DOT redhat DOT com
Subject: Re: Cygipc, Postgresql, etc ...
References: <CD62E40B9F85D3118C490060B08744EF6BE13B AT ftp DOT biosgroup DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Valerio Aimale wrote:
> 
> I guess it's the maintainer of the cygutils site
> 
> http://cygutils.netpedia.net/
> 
> http://cygutils.netpedia.net/V1.1/index.html
> 
> ---

Errmmm...that's me. If hosting the package on a reliable server and
accepting patches from other folks makes me the "maintainer" then I
guess I am. My view of a *real* maintainer of a unique package(*) is
someone who (a) understands the code (b) wrote a good portion of the
code (c) can evaluate patches based on a thorough understanding of the
operation and the ramifications of each patch. 

That ain't me.

(*) unique package: like cygIPC, a unique piece of software intended for
use on a single platform. Normal *ports* are a little easier to deal
with: for instance, libpng has a whole host of developers from multiple
platforms working on it daily. I just try to insure that libpng builds &
works on cygwin, and maintain small external patches to enable that --
and sometimes pushing those patches into the official png-developers
distro.

Anyway, if someone out there is able to be more proactive than I am in
"maintaining" cygIPC, I'll gladly hand it over -- heck, it's open source
and everything I've got is on the web site already, so anyone could
start taking a more active role right now if they really wanted to.

An attractive alternative, of course, is to put cygIPC onto sourceware
CVS and let everybody start hacking on it. I've just been a bit
overwhelmed lately trying to get many of the CygUtils packages built for
inclusion in the 'latest' or 'contrib' directories...and there's this
pesky dissertation to write.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com