hi Kevin, I stated in a previous e-mail that I would maintain the JOE package (haven't uploaded the definitive package yet because I've had some extremely busy weeks, sorry). It's a package that updates quite rarely, so I guess I'll have time for maintaining cURL too...
If noone volunteers, tell me and I'll take it Saludos, --- Ricardo Varela http://phobeo.com > I'm no longer interested in taking care of the cURL package; are there > any volunteers available to take my place? > > It generally builds 100% clean OOTB, so there's rarely any issue; I just > lack the minimal time to keep up with it, and also lack the coding > experience necessary should there ever be a cygwin specific problem to > be fixed (or new feature to support). > > A rudimentary build target is in place in the upstream sources to handle > building the Cygwin tarballs. It's not perfect, but it's use is > documented in the package's cygwin README. That readme is also kept in > the upstream sources, in a sub-folder named packages/Win32/cygwin/. > > The primary developer (Daniel Stenberg) is very active on the cURL > mailing list, and is highly responsive when needed. > http://curl.haxx.se/. He keeps a listing of all current builds, so in > addition to uploading new Cygwin builds to cygwin.com, it would be nice > to either load them onto curl.haxx.se, or at least let Daniel know about > new versions at cygwin.com so he can link to them there... > > Anyone? Anyone? Buehler? > > Thanks, > - Kevin
