This sound just right to me.

Kindly,
Robert

On Fri, Jun 5, 2020 at 23:25, Chris Cunningham <cunningham.cb at gmail.com> wrote:

> Hmm.
>
> So what would be the behaviour if the embedded config had the same package specified as the outer config, but with a different version?
>
> Easiest would be to just do them in order:
> Load Package A.2
> Load Embedded Config (which load Package A.1, and Package B.4)
> Load Package B.3
>
> At the end, you'd end up with A.1 and B.3.
>
> Does the current (i.e., enhanced) version of Monticello configurations keep track of the latest one loaded into the image?  And which repository it came from?  If so, this shouldn't be excessively hard.
>
> However, please never ever do this in the main trunk configuration map!
>
> -cbc
>
> On Fri, Jun 5, 2020 at 8:07 AM Robert Withers via Squeak-dev <squeak-dev at lists.squeakfoundation.org> wrote:
>
>> Hello,
>>
>> Someone is working on Monticello configuration maps, I think it is David
>> Lewis. David, would it be possible to add the feature that a config map
>> can load another config map? I want to set ProCrypto-1-1-1 map to be
>> loaded by PromisesLoader, loading remote promises.
>>
>> K, r
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200606/9df81afd/attachment.html>