This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Cygipc, Postgresql, etc ...


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@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]