0:09:52jcowanIf you had a sandbox, you could statically examine what it does and see if you are willing to load it into the live image, but of course there are no guarantees about what crimes it might commit dynamically.
1:08:22no-defun-allowedalso, erm, can i get a worker id from lparallel workers?
3:17:45r0sebushquestion from a sbcl newbie.. What's is the best method to include libraries, like cl-ppcre into your lisp code for production release? .sbclrc or include (ql:quickload ...) in your code base?
3:39:19gendl1. have a .asd file for your application which has a :depends-on (:cl-ppcre ...)
3:39:49gendl2. When ready for release, use (asdf:operate 'asdf:monolithic-compile-bundle-op <your-application-system-name>)
3:40:24gendlthat will produce one big .fasl with your whole application including its depended-upon stuff, presumably in the right order.
3:40:52gendlthen start a fresh sbcl image, load this .fasl, then dump image. (I'm not sure the specifics of that with sbcl). ASDF also has built-in operators for doing that.
3:41:43gendlSee this ancient blog post which needs to be updated/added to: http://gendl.blogspot.com/2013/03/saving-images-with-asdf3.html
3:43:37gendlit was suggested earlier today that someone needs to make a do's-and-don'ts for production application release and maybe a how-to. It's something which should be pretty routine and well known at this point but doesn't seem to be.
5:45:44no-defun-allowed- use burgled-batteries to interface python module that interfaces opencv for images
6:22:44no-defun-allowedstill, most of this box-mangling and vision stuff would read better in lisp but common-cv is just a very fine wrapper over C unfortunately