4 ms·
I'm not sure this is a great idea. I have a couple projects in QuickLisp, and more than once I've broken them after I pushed incremental or non-working changes
by jlarocco 7y ago
I'm not sure this is a great idea.
I have a couple projects in QuickLisp, and more than once I've broken them after I pushed incremental or non-working changes to my repo, didn't go back and fix them in time, and QL pulled the broken code.
Developing in branches would solve the problem, but not everybody does that on smaller informal projects.
On the other hand, I've also been annoyed waiting for bug fixes to trickle through to Quicklisp, so it's not an entirely bad idea...
- phoe-krk 7y agoThe bleeding edge isn't for everyone. But then again, neither are monthly releases.
- svetlyak40wt 7y agoPinning libraries using Qlot solve the issue of being on the bleeding edge.
- Grue3 7y agoMonthly releases + a few bleeding edge libs strategically cloned into /local-projects is the best strategy.