MonticelloConfigurations - configurations of configurations?
Bert Freudenberg
bert at impara.de
Tue Nov 22 13:03:14 UTC 2005
Am 22.11.2005 um 13:11 schrieb Cees De Groot:
> On 11/22/05, Bert Freudenberg <bert at impara.de> wrote:
>> Until now, in the spirit of TSSTCPW, MCConfigurations are a flat list
>> of versions (MCVersionDependencies, to be precise).
>>
> I've seen that. But, theoretically, because the interface of an MCM
> and an MCZ w.r.t. loading seems to be the same, it should be possible
> to put a pointer to an MCM in a configuration, no?
MCConf mimics MCVersion to the extent that some MCTools work with
both, like the repository browser. But, for example, MCConfs are not
yet versioned, do not have a UUID nor a package, etc.
But sure, you could try that. The Right Thing To Do would be
refactoring MCVersion and MCConfiguration to share the dependency
handling and versioning (perhaps in a common superclass) and make
them interchangeable. MCVersion would add the code snapshot, and
MCConfiguration the repositories, maybe, though that doesn't really
fit in there.
- Bert -
More information about the Squeak-dev
mailing list
|