MCConfigurations quick how-to
stéphane ducasse
ducasse at iam.unibe.ch
Thu Nov 24 12:57:06 UTC 2005
I agree with what avi was saying.
Basically you want to have a working set = load the latest and a
release (where you freeze the version numbers).
There were some discussions with reinout on VW and he has lineUp that
are external to the package.
> If someone has an idea for a system and interface to manage
> multiple, possibly versioned configurations, I'm all ears. It's
> just that I did not need it until now.
For me I would like to be able to tage one as 6704
>
> Avi also had to say something about this (http://mail.wiresong.ca/
> pipermail/monticello/2005-February/000121.html):
>
> "From the point of view of architecture: what I think I'd ideally like
> to see is a Configuration object that is completely separate from
> Version objects, whose interface is very simple - it just returns a
> list of versionInfos. Versions themselves wouldn't have any
> dependencies at all, loading and saving one simply means loading and
> saving that package. Then we could play with having a number of
> different types of Configuration that found that list of versionInfos
> in different ways - one that found the latest version of a set of
> package names, one that had hardcoded versions, one that found the
> latest version in a particular repository or on a particular branch,
> etc. It should be fairly easy to do that as a layer above all the
> current version/workingcopy stuff so that it's not intrusive at all."
>
>
> - Bert -
>
>
>
More information about the Squeak-dev
mailing list
|