On 15.08.2013, at 18:48, Chris Muller <ma.chris.m at gmail.com> wrote:

> On Thu, Aug 15, 2013 at 11:39 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>> It happens to not find "XML-Parser-Alexandre_Bergel.20". No idea why it's trying to look for that. Not all merged versions are in trunk, by design.
> 
> The original MC documentation says ALL versions are intended to be contained by repositories.  I have no idea what "design" you're talking about.

The idea is that versions are self-contained. When I merge two versions, I only need to share and upload the result. That means that you will not find that other version in your repo. But the merged version has all ancestry data in it (you know that).

>> The more I think about it, the less convinced I am is that this space optimization is worth introducing such a fragile
> 
> You uncovered one issue and you're calling it "fragile?"  Proxy is a well-documented, proven pattern that has stood the test of time.

I'm not aware of any current use of proxies in Squeak trunk. 

>  machinery. MC is designed to have all ancestry info available at all times - just opening any repository will cause the proxies to materialize again, because the highlighting looks at which version names are in the ancestry of the working copy.
>> 
>> I'd rather revert this whole thing, to be honest. If you're trying to build a minimal image for deploying an application you would be better off unloading MC altogether.
> 
> 
> It's not just about smaller images.  It's about sustainability of the ancestry.

But as soon as you use MC it needs the ancestry anyway. 

- Bert -

>> 
>> - Bert -
>> 
>> On 2013-08-15, at 18:26, Chris Muller <asqueaker at gmail.com> wrote:
>> 
>> > Ok, I'll look at it today.  One thing is that all ancestry SHOULD be
>> > in the same repository -- but I agree, the system needs to handle that
>> > as gracefully as possible if it isn't.
>> >
>> > Can you tell me how to reproduce the issue?
>> >
>> > Thanks.
>> >
>> >
>> > On Thu, Aug 15, 2013 at 10:39 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>> >> It's not quite bullet-proof yet: log of DNU attached. It fails to find a certain info, which causes all kinds of problems.
>> >>
>> >> Also, something apparently tries to materialize infos in the background. Possibly updating MC browsers, not sure. This leads to very strange and hard to get-rid-of notifiers:
>> >>
>> >>
>> >>
>> >>
>> >> (these updating bars used to be very rare, like once per session, recently they pop up multiple times for many operations, but I've never before had 2 on the screen at the same time)
>> >>
>> >> - Bert -
>> >>
>> >>
>> >>
>> >>
>> >
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20130815/e75e0b23/attachment-0001.htm