Yeah I'm doing that for my main USMRS package.  But I also load up Seaside,
SeasideAsync, Cees' tric stuff, Glorp, PostgresV2, a bunch of cryptography
stuff and more, and I want to know when something changes anywhere.  Plus I
load this frequently to a virgin image to make sure I can load everything up
properly.  Monticello Configurations is wonderful for this!

Ron

> -----Original Message-----
> From: Avi Bryant [mailto:avi.bryant at gmail.com]
> Sent: Monday, November 20, 2006 2:30 PM
> To: Ron at usmedrec.com; The general-purpose Squeak developers list
> Subject: Re: RE: Broken SqueakSource?
> 
> On 11/20/06, Ron Teitelbaum <Ron at usmedrec.com> wrote:
> >  I have no idea
> > how people use Monticello without using Monticello Configurations!  (I'd
> be
> > completely lost without it)
> 
> FWIW: what we do is to have a single package with no actual code, with
> dependencies on every other package our application needs (this is a
> flat dependency tree, not nested).  When developing, we commit new
> versions of the lower-level packages as needed.  When we want to
> release something, we sync up everyone's changes and then commit a new
> version of the top-level package.  That gets loaded by everyone and
> becomes the basis for a new round of changes.
> 
> Avi