4 ms·
For https, we can now use the newer Lisp Package Manager: https://gitlab.common-lisp.net/clpm/clpm https://gitlab.common-lisp.net/clpm/clpm (or use a mitm proxy
by vindarel 4y ago
For https, we can now use the newer Lisp Package Manager: https://gitlab.common-lisp.net/clpm/clpm https://gitlab.common-lisp.net/clpm/clpm (or use a mitm proxy: https://hiphish.github.io/blog/2022/03/19/securing-quicklisp-through-mitmproxy/ https://hiphish.github.io/blog/2022/03/19/securing-quicklisp... )
- oblio 4y agoIt looks interesting, however this is a bit scary: > WARNING: This software is BETA quality. I use it as my daily driver, but it is still a little rough around the edges and it may accidentally eat your files. And for QuickLisp, this is scary: https://github.com/quicklisp/quicklisp-client/issues/167#issuecomment-394423049 https://github.com/quicklisp/quicklisp-client/issues/167#iss... > It would be good to do, but there's no straightforward path to do it. Implementations do not all provide HTTPS support, it's not straightforward to make it from scratch or use HTTPS libraries on all supported platforms. The fact that the package manager (!!!) isn't able to ensure use of HTTPS libraries as its own dependency on all platforms is... super scary.
- vindarel 4y agoLPM's warning is not surprising. It's common for libraries (dare I say open-source ones?), even if they work well. It's part of the stability game, once they are marked 1.0, they are stable. LPM works well (as reported by others). QL wants to do it portably, there are easy workarounds, but yeah… (just saw https://github.com/rudolfochrist/ql-https https://github.com/rudolfochrist/ql-https)