>>   
> Keith,
>
> I patched your MCConfiguration patch (published to ss) and now the
> configuration loads on the simple test cases I was using before.  Now
> I'm having a new problem, the class initialization order is somehow
> messed-up.  
I hear echoes of "I told you so" coming from Matthew!
> My code doesn't assume anything about the order of sending initialize
> to classes in an individual package but my system (actually a package
> that my system uses) assumes that packages loaded before it have been
> initialized.  I think that's a reasonable expectation.  Using the
> older MCConfiguration>>#load (djr.48), I get the correct
> initialization behavior.
....
> So, the original patch + the older MCConfiguration>>#load is good
> enough for me for now.  The patched Installer>>mcThing doesn't work
> correctly if multiple packages, one of which is an MCM, are being
> loaded but I think it will take a bit more design thinking to get that
> case right.
Fair enough

Keith