I have merged Fare's RUN-PROGRAM topic branch and pushed it as 3.0.2.11. Passes all the tests for Fare and me on Linux and for me on Mac (modulo known bugs in bundle-op).
My intention is to release this as 3.0.3 in the next few days, but I would like to make it available for people to play with first.
I'm of course happy for you all to run the test suite on your own machines and implementations (contact me if you need help setting this up), but even more, I'd be obliged if you were to test this on your own systems (again, ask for advice if you need help setting up to do this). I'd particularly urge you to try this on systems where you have made your own extensions (new component or operation classes), or where you reach out into the environment to do something else (e.g., run "make" or the C compiler for FFI). Those would be the most likely to expose bugs in the new facilities.
Best, r
On Thu, Oct 3, 2013 at 12:22 PM, Robert P. Goldman rpgoldman@sift.info wrote:
I have merged Fare's RUN-PROGRAM topic branch and pushed it as 3.0.2.11. Passes all the tests for Fare and me on Linux and for me on Mac (modulo known bugs in bundle-op).
Thanks a lot! I deleted the topic branch from the git repo (it was at c8487c61a760a5dc2844e02312920e795b2f0ba7 which is part of master, so no information was lost).
I've also rebased the package-system branch on the git repo (so, delete it before you pull it again, or rebase it). I don't expect you to merge it before the 3.0.3 release, but it would be nice to have it merged right afterwards: it's additive stuff, no one should notice.
My intention is to release this as 3.0.3 in the next few days, but I would like to make it available for people to play with first.
I'm of course happy for you all to run the test suite on your own machines and implementations (contact me if you need help setting this up), but even more, I'd be obliged if you were to test this on your own systems (again, ask for advice if you need help setting up to do this). I'd particularly urge you to try this on systems where you have made your own extensions (new component or operation classes), or where you reach out into the environment to do something else (e.g., run "make" or the C compiler for FFI). Those would be the most likely to expose bugs in the new facilities.
It would be especially nice for anyone calling an outside compiler to use uiop:run-program instead of reinventing the wheel. e.g. cffi-grovel, iolib-grovel, etc.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Your denial of the importance of objectivity amounts to announcing your intention to lie to us. No-one should believe anything you say. — John McCarthy
-
Faré -
Robert P. Goldman