On Thu, 18 Sep 2003, Mark A. Schwenk wrote:

> I'd like to be able to pull all the packages from SqueakMap I need into
> my local repository so that I can track changes the authors make as well
> as changes I may need for my application.

Assuming we're talking about Monticello packages, there's no problem with
this.  When you make local modifications, just save those modified
packages locally.  When the author releases a new version, you can merge
it in.  Because the ancestry tree is stored with each version,
and not per-repository, it's just as easy to merge code from separate
repositories as it would be if all the versions were kept centrally.

Monticello also doesn't have the "multiple-merge" problem that CVS
exhibits - you can merge the mainline into your branch as many times as
you like without having to deal with spurious conflicts.

> In addition to these items, I'm wondering how to handle grouping of
> packages into larger entities, such as "all the packages I need for this
> application I'm building." I'm not sure if Monticello yet has this
> concept for a set of packages or set of versions of packages.

It doesn't.  As Ned points out, SARs are one way of managing this
externally to Monticello.  I'd also like to introduce some kind of notion
of tagging (so you could have a tag "MyApp-v2" that would refer to all the
package versions that made up that app version), but don't have a clear
design in mind yet.  Suggestions are welcome.

Avi