monticello with dependencies

Avi Bryant avi at beta4.com
Tue Jan 20 10:30:34 UTC 2004


Lukas,

Thanks much for the feedback.  Just a quick reply before I go to sleep:

On Jan 20, 2004, at 2:17 AM, Lukas Renggli wrote:
>
> - I created an empty package 'Root' and two dependent packages 'RootA'
> and 'RootB' with an empty class in each. When trying to save 'Root' for
> the first time I get the following stack-dump:

Yup, known bug, I'll try to fix it tomorrow.

> - The dependent packages do not get properly stored in the repository,
> loading from the same image works however as it is loaded from the 
> cash.
> I don't see what the problem is actually, because I assigned the same
> repository to the dependent packages but they do not appear there.

Actually there was some thought this might want to be configurable - 
whether to always save dependent versions in the same place as the 
bundle/whatever version or not.  For now they just get stored to the 
cache, but I think I will probably change the default to be what you 
evidently expect, that everything gets stored to its default repos.

> - I accidently added the same dependency 'RootA' twice to the package
> 'Root', something that should probably be avoided eventough it doesn't
> lead to problems:

Yup, I'll have it check for that.

> And some cosmetic question: Why do you show the dependencies below the
> comment? I would prefer to have it in the block with all the 
> information
> above.

Cause that was the quick and dirty way to do it :).
>
> - A detail: When modifying a package, the appearing star in the 
> modified
> item makes it appear at the very top of the list. I would prefer to 
> have
> it always in the same order. And another idea: shouldn't be a star also
> displayed in the package that is dependent on the modified one?

Both good ideas.

> Ok, that's it for the moment! Sorry not to come with a ready to merge
> solution, but I have a few ideas to enhance the repository browser to
> visualize the new meta information.

Excellent. :)

Avi




More information about the Squeak-dev mailing list