Somehow I just now noticed the followups to this thread, sorry for the late response. I would like to keep the thread alive though.

I was hoping to have that done and submit the immutable-systems patch before the next major release, but obviously I'm too late for that now -- I happen to be starting the Windows tests for 3.1.4.13 right now, which are apparently the last hurdle for a 3.1.5 release, and I certainly don't want to suggest holding up the 3.1.5 release by trying to cram the immutable-systems patch into it. After 3.1.5 is out the door I will attempt it during the subsequent window of opportunity.

I admit I've been shipping my immutable-systems patch privately with the asdf shipped with Gendl and GDL pre-built distributions since last summer. This is obviously dangerous practice on our part and has to stop.

On Tue, Aug 26, 2014 at 1:52 AM, Faré <fahree@gmail.com> wrote:

On Mon, Aug 25, 2014 at 7:39 PM, Robert P. Goldman <rpgoldman@sift.info> wrote:
> Has there been any more progress on this front, since 11 August? That
> was the last email I saw on the subject.
>
Dave and I had a brief conversation about it at ILC 2014. My advice
was to modify test-bundle.script and not bother with subprocesses,
just with detecting side-effects in a .asd file (defpackage or
defparameter), and undoing it (if needed) before the next test:
compare the situation before and after making the bundle, undo
effects; compare the situation before and after loading the bundle,
undo effects; mark the systems immutable, touch for modification;
compare the situation before and after trying to update. Repeat the
test without marking the system immutable.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
I hold that America, Champion of the World is a betrayal of
its humble beginnings as One Nation Underdog.

My Best,

Dave Cooper
genworks.com, gendl.org
+1 248-330-2979