> libwget from GNU Wget2 is a better alternative. It is a GNU > project and shares the libgnutls dependency with Emacs. Are you sure about that one? https://gitlab.com/gnuwget/wget2/-/wikis/GNU-vs.-non-GNU However, Emacs already links against other non GNU libs, I am not sure it is an argument. Curl can use gnutls if desired, but maybe Emacs can get rid of gnutls dependency if using libcurl for the network stack? Libcurl is well known, tested and well documented (there are even books about it); libwget seems like new as a library. I don't know, I am not familiar with libwget, didn't know wget had an API and a library; they didn't used to before. Maybe it is technically better then libcurl, it can be worth investigation. Whichever emacs devs would use I think it would be nice to have a good networking stack accessible from elisp. ________________________________ Från: Emacs-devel för Vladimir Sedach Skickat: den 29 mars 2021 00:42 Till: T.V Raman Kopia: Daniel Brooks ; Adam Porter ; emacs-devel@gnu.org Ämne: Re: Emacs HTTP libraries [was: Re: How to contribute new package to GNU ELPA?] T.V Raman writes: > Daniel Brooks writes: > > 1+ on libcurl, this discussion happened a while ago here though and ran > aground, dont remember why. > But independent of the ability down the road to native-compile elisp, I > still think re-using the work of the curl project to get an HTTP library > that the emacs project doesn't have to maintain would be a big win libwget from GNU Wget2 is a better alternative. It is a GNU project and shares the libgnutls dependency with Emacs. -- Vladimir Sedach Software engineering services in Los Angeles https://oneofus.la