How-to Monticello Configuration

Philippe Marschall philippe.marschall at gmail.com
Thu Mar 8 05:43:49 UTC 2007


We don't have the moving problem (we build our images every night from
scratch) but we do have the initialization problem. So the choice is
pretty simple to us. The change provides no value to us only problems.

Philippe

2007/3/8, Ron Teitelbaum <Ron at usmedrec.com>:
> I definitely agree with Bert.  This really is a terrific solution and I have
> found it to be very useful.  When I find a problem in code, I fix it and
> store the next numbered version in my own repository.  My code loads
> automatically until a new version of the package is released, hopefully with
> my suggestions added.  It's really cool.
>
> Ron
>
> > -----Original Message-----
> > From: squeak-dev-bounces at lists.squeakfoundation.org [mailto:squeak-dev-
> > bounces at lists.squeakfoundation.org] On Behalf Of Bert Freudenberg
> > Sent: Wednesday, March 07, 2007 6:21 PM
> > To: The general-purpose Squeak developers list
> > Subject: Re: How-to Monticello Configuration
> >
> >
> > On Mar 8, 2007, at 0:07 , Philippe Marschall wrote:
> >
> > > 2007/3/7, Bert Freudenberg <bert at freudenbergs.de>:
> > >> On Mar 7, 2007, at 23:37 , Philippe Marschall wrote:
> > >>
> > >> > With MCC the specified Monticello versions are loaded in the given
> > >> > order from the given repositories.
> > >>
> > >> Well, actually, I changed that about a year ago in the impara
> > >> version:
> > >>
> > >>         http://source.impara.de/mc.html
> > >>
> > >> It solves the problem of moving stuff between packages. Without that,
> > >> moving methods or classes between packages is impossible to do
> > >> correctly.
> > >
> > > But creates a new one when a package assumes an other package is
> > > present and initialized. As a result strange things may happen in
> > > class side #initializes, and actually did happen for some of our
> > > projects so we reverted that behavior.
> >
> > Well, there are workarounds for the init problem. There is no
> > workaround for the moving problem, except for manually fixing up
> > things when it's to late. So I'd opt for the former - but YMMV of
> > course.
> >
> > - Bert -
> >
> >
> >
>
>
>
>



More information about the Squeak-dev mailing list