cURL packaging progress

Roth, Kevin P.
Tue Oct 16 13:27:00 GMT 2001

Considering it appears I was BCc'd (and the list wasn't copied), I'm
responding just to you two. 

I believe curl will be completely cygwin compliant (with all necessary
readme's, etc) as it is distributed from For this reason,
I could do one of two things for submitting source tarballs to cygwin
(once curl is accepted as an official package):

1: submit in original form (meaning it will unpack as curl-7.9.1),
   we could easily change the name of the tar file to match.

2: download, untar, 'mv curl-7.9.1 curl-7.9.1-1', retar. This sounds
   more work, considering I would "typically" never expect to make any
   cygwin releases that didn't correspond to new curl releases. In other
   words, in most cases there will never be a curl-7.9.1-2.

I'm guessing #2 is your preference, however I'm just wondering if you're
open to accepting #1 in this case (obviously if there WERE a need to
release an interim cygwin version, it would then have to be named
appropriately and repackaged...)


> -----Original Message-----
> From: Charles Wilson [ ]
> Sent: Tuesday, October 16, 2001 4:18 PM
> To: Corinna Vinschen
> Subject: Re: cURL packaging progress
> Corinna Vinschen wrote:
> > Oops, Chris missed the release number in the example:
> > 
> >   curl-1.2.3-1.tar.bz2
> > 
> > The source analogous
> > 
> >   curl-1.2.3-1-src.tar.bz2
> > 
> > The source should unpack into a directory exactly named as the
> > archive
> > 
> >   curl-1.2.3-1/
> Oops. I didn't know this. I've been doing <srctop> = curl-1.2.3, not 
> curl-1.2.3-1.
> --Chuck

More information about the Cygwin-apps mailing list