FWIW a prototype GUI for quicklisp that clarified some of these dist/release/system issues for me (also ASDF systems vs quicklisp systems)... Perhaps it could be of some utility, especially for newbies...Am interested in feedback beyond what I have already received and incorporated from the McCLIM developers' list (i.e., bugs, usability, etc.)In particular:
- I have noticed dists other than quicklisp itself (e.g, bodge and shirakumo) tend not to provide version history/availability info - how best should the GUI (or indeed any user) infer such a dist is out of date?
- I should probably, upon request, present (in a popup) the list of changes/updates that an update-dist would make, in some sort of popup as a separate command (rather than the confirmation step of an actual update-dist), and
- I should probably popup the confirmation itself of such actions
While I've been using it myself for some time, please be advised that it does actually invoke quicklisp operations that will result in changes...-jmp.s., althoughOn Wed, Dec 27, 2017 at 11:09 AM, Zach Beane <xach@xach.com> wrote:There can be more than one dist, but "quicklisp" names essentially the default dist. There are others - http://bodge.borodust.org/dist/org.borodust.bodge.txt for example has a dist named "org.borodust.bodge" that has trivial-gamekit software. You can install it with (ql:install-dist "http://bodge.borodust.org/dist/org.borodust.bodge.txt ") and update it with (ql:update-dist "org.borodust.bodge") or (ql:update-all-dists). Going back in time doesn't work, though.ZachOn Wed, Dec 27, 2017 at 10:50 AM, Ken Tilton <kentilton@gmail.com> wrote:Oh, wow: update-all-dists *does* update all dists. Yes, big hammer.Not sure I get the naming here: (ql:update-dist "quicklisp").Could that be update-current-dist, taking no params? What values other than "quicklisp" make sense. Meanwhile, I (again belatedly) looked at http://cliki.net/Quicklisp%20tutorial . I imagine (ql:update-client) does more than I realized? Mebbe not. Anyway, back to work...-ktOn Wed, Dec 27, 2017 at 10:30 AM, Zach Beane <xach@xach.com> wrote:I don't recommend using update-all-dists as the default. I prefer to recommend (ql:update-dist "quicklisp"), which updates all projects in the quicklsp dist.There can be multiple dists installed, and update-all-dists calls update-dist on all of them.See blog.quicklisp.org for news about what is updated each month.ZachOn Wed, Dec 27, 2017 at 10:27 AM, Ken Tilton <kentilton@gmail.com> wrote:Thanks, Luis! I noticed update-all-dists too late, not sure how I missed it. I bravely attempted (ql:update :cffi) but of course no luck, I guess because you are saying:A
dist is, among other things, a list of URLs pointing to project
snapshots that are known to work well with each other.But then the name "update-all-dists" seems off (checking my understanding). Does it not update-all-*projects* in the one current dist? Trying to answer my own question on The Google, I found this gem of a thread:...and the extensive :ql-dist package.I guess I should not have skipped the instruction to contact Xach if I had any questions. :)Thanks again, hk--On Wed, Dec 27, 2017 at 5:53 AM, Luís Oliveira <luismbo@gmail.com> wrote:On Tue, Dec 26, 2017 at 7:43 PM, Ken Tilton <kentilton@gmail.com> wrote:
> But I am curious, I will first try to see why uninstall did not work.
When you first install Quicklisp, it will download the latest dist. A
dist is, among other things, a list of URLs pointing to project
snapshots that are known to work well with each other. (This is one of
the key features of Quicklisp!) Uninstalling a project then
reinstalling it doesn't achieve much since Quicklisp will again grab
the very same project version, as determined by the dist.
To update to the latest dist, you can use ql:update-all-dists. They're
released monthly.
Cheers,
--
Luís Oliveira
http://kerno.org/~luis/
Kenneth Tilton