Hi,
I yesterday put Pharo Kernel Gofer 2.0 job into operation (together with some other dependent like Seaside and OSProcess evaluator). But unfortunatelly I have to say it was quite complicated and I had to do some ugly hacks because we do not have solved dependencies between Monticello, Ring and RPackage.
The loading order we use now is: 'Monticello' 'MonticelloConfigurations' 'Ring-Core-Kernel' 'RPackage-Core' 'RPackage-SystemIntegration'
Pavel this is strange because RPackage was always managed using Metacello. Now we should fix the dependencies.
Authors of this packages should know that this are primitive packages that cannot be loaded in one bundle via Monticello but must be loaded one by one as standard *.st files. That means that that we have to have well known and working loading order. As an example, currently the initialization of the package 'RPackage-Core' is dependent on presence of 'RPackage-SystemIntegration'.
Cheers, -- Pavel