David Steuber <firstname.lastname@example.org> wrote:
| email@example.com (Rob Warnock) writes:
| > ;;; Boilerplate for using ASDF from LHP page.
| > That way, ASDF verifies that everything's up to date and (re)compiled
| > on *every* web hit. That makes the development cycle *very* tight:
| > edit a bit, do a "save" in the editor, hit "Reload" in the browser,
| > and *boom*! Everything gets recompiled and the browser pops up the
| > new version of the page. [Or doesn't, and I look at the application
| > server's REPL and/or the Apache error log to figure out why.]
| Do you ever get bitten by dependencies that exist in your image but
| have been elided from the source?
Yes, but it's fairly rare. And anyway, I do my development on a laptop
[yes, that's running Apache & PostgreSQL as well as CMUCL and a browser],
so it gets rebooted anyway whenever I shut it down. Only when the new code
works as desired is it copied to the production site. [And tested again,
at least briefly...]
| I'm always paranoid about that which is why I go back and rebuild
| my whole image from scratch from time to time. I have actually
| had that issue. I've also had weird order dependencies (a result
| of me not fully understanding the package system) where I had an
| image that just wouldn't build from the existing source.
Yes, all that happens, rarely, but not often enough to get "paranoid"
Rob Warnock <firstname.lastname@example.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607