=== ----- Original Message ----- >From: "Roth, Kevin P." <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, November 16, 2001 2:21 AM >Subject: [RFP] cURL (was: It's official -- package moratorium lifted) > >
>Name: cURL > > (NOTE - this binary was compiled and built with no changes > to the source. Would it be too much to ask that whoever Does it handle textmode issues? > Once all the packaging style issues are settled, I'll be > happy to follow the new standard; until then it's just > so much simpler for you to make this tiny change, than > for me to do so, and then obtain a free web-hosting location > just for this...) See my comment to Gareth about nano - I had my wires crossed and address'd this point there. I will accept a direct email from you as curl is nice and small. Also, you have veered from the CYGWIN-PATCHES standard, which until we have a new one, is a bad thing. And because your readme is in the binary, there is no obvious way for someone building from source to find it. IMO this definately needs changing. (Not saying I _like or dislike_ CYGWIN-PATCHES, but it is consistent). >setup.hint (I will be submitting this upstream once it's approved) There is no reason for setup.hint to be in the vendors source, it's a cygwin _packaging_ specific thing. Of course it is up to you :}. >sdesc: "cURL groks URLs" ># sdesc could also be "a client that groks the URLs", ># if you think it's important not to restate the ># package name in the sdesc... Or, " groks URLs". That should dispaly as "curl: groks URLs". >ldesc: "Curl is a tool for transferring files with URL syntax, >supporting >FTP, FTPS, HTTP, HTTPS, GOPHER, TELNET, DICT, FILE and LDAP. >Curl supports HTTPS certificates, HTTP POST, HTTP PUT, >FTP uploading, kerberos, HTTP form based upload, proxies, >cookies, user+password authentication, file transfer resume, >http proxy tunneling and a busload of other useful tricks." >category: Web Net Libs >requires: openssl Is curl cygwin linked? if so, then cygwin is a requirement as well. Rob
