Re: Shipping wcurl in curl tarballs?
Samuel Henrique via curl-library <[email protected]>
| Newsgroups | gmane.comp.web.curl.library |
|---|---|
| Message-ID | <meej2d6bbgmpjhbkmppfpz3berm4eidesqnc2sp6ftlczkyvn2@zyanq2z7wydm> |
Hello, On Tue, 18 Feb 2025 at 15:15, Daniel Stenberg <[email protected]> wrote: > What I think further complicates the matter: I know that there is talk and > perhaps even plans, to make a wcurl implementation in C (or rust?) one day > that compiles against libcurl to A) give it more powers to do things that are > hard to realize in the current shell script version and B) make it independent > of shells and thus make it run on more platforms. > > If we imagine that the plans work out and such an incarnation of wcurl > appears; it feels instinctively wrong to bundle that version with curl. And > maybe if it does appear and we already while wcurl with curl, does that > perhaps makes things even more complicated for users than otherwise? I like to think that it does make sense to keep shipping the wcurl script, even after there's a compiled wcurl (if it happens), because the wcurl script fulfills the needs of most people (recursive downloads is common but not the majority) and it's easier to install, but I understand this is not a simple decision. Would questions like these be a good fit for the curl survey? * Would you prefer wcurl to always be installed together with curl? * Are there features that you miss from wcurl? * If we provide a wcurl that needs to be compiled, with more features, would you still see value in the POSIX shellscript wcurl? Cheers, -- Samuel Henrique <samueloph> -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html