Philippe is entirely correct. In fact, the entire MCC file is just a  
literal array without the # marks. You can create an actual   
configuration object by pasting "MCConfiguration fromArray: #" before  
it. Or, you can create a changeset that upgrades to a certain  
configuration like this:

(MCConfiguration fromArray: #(
    ... config here ...
)) upgrade

- Bert -

Am 13.10.2006 um 21:52 schrieb Philippe Marschall:

> 2006/10/13, stephane ducasse <stephane.ducasse at gmail.com>:
>> Hi bert
>>
>> I forgot. Sorry if you already say it: is the mcc format saving
>> complete packages so just the differences on the server?
>
> No, not at all.
> A Monticello configuration map includes only the name, uuid (in newer
> versions) and order of versions and a list of repositories. It's just
> metainforamtion.
> (Sorry, I know this explanation sucks)
>
> It can be stored anywhere independently of the versions it references.
>
> Its only a small and simple textfile. Open it with a text editor and
> things will become much clearer.
>
> Philippe.
>
>> On 10 oct. 06, at 19:49, Bert Freudenberg wrote:
>>
>> > Am 10.10.2006 um 15:30 schrieb Stéphane Ducasse:
>> >
>> >> hi bert
>> >>
>> >> I would like to know
>> >>      - if I can publish mcc files on a source?
>> >
>> > You mean, a squeaksource server? Yes, should work, I think Philippe
>> > merged my support for this into your installation.
>> >
>> >>      - should all the packages be published in the same server?
>> >
>> > Not necessarily, that's why you can add repositories to the config
>> > map.
>> >
>> >
>> > - Bert -
>> >
>> >
>> >
>>
>>
>>
>