On Mar 17, 2006, at 7:28 AM, Bert Freudenberg wrote:
>
> The problem appears to be MCPackageLoader, which does not check the  
> list of removals against the list of additions.
>
> I fixed that (hopefully) in Monticello-bf.279 (http:// 
> source.impara.de/mc.html). If there are more than one versions  
> loaded at once, then an additional step is taken to detect and  
> delete those removals that are also added. Would be nice if someone  
> could comment if there is a better way to do this, but I believe  
> it's not too bad. You only pay the price if indeed there is more  
> than one version to be loaded.
>
> I actually discovered this bug (though we had occasional reports  
> about lost methods) when making MCConfigurations use a simultaneous  
> load strategy (see MonticelloConfigurations-bf.38). With this fix,  
> configs now should be able to deal with methods or classes moved  
> from one package to the next, and be pretty independent of order  
> problems. Perhaps using this could also help the 3.9 team switching  
> to a more efficient work flow, even without the flaws I outlined  
> last year (http://lists.squeakfoundation.org/pipermail/squeak-dev/ 
> 2005-October/096445.html).

Cool.  This sounds similar to the fix that Daniel and I struggled  
with (causing similar grey hairs) back in October for merging, so  
it's good to get it working for loading too.  Moving stuff between  
packages has always been a major PITA...

Avi