MC copying bug

So, by logging into the server, carefully monitoring the actual
directory contents, I think I see what's happening.

I thought maybe something wrong with my ReleaseBuilder
class>>#transferCurrentPackagesAsUser:password: I used to conveniently
put the baseline versions for 4.5 into the 'squeak45' repository,
because some of the packages appeared to be empty.

So, using just the MC UI by hand, I opened 'trunk', selected
Tools-cmm.519(cmm.518).mcd and copied it to 'squeak45'.

Can we copy .mcd files?  Apparently not -- SqueakSource treated it as
a MCZ and wrote out the contents of the mcd but under the name
Tools-cmm.519.mcz.  Once there, its hard to get rid of.

Until we can get this fixed, please be careful not to copy MCD files!

Another observation, every time a new package is saved, SqueakSource
produces a .mcd diff with its ancestor.

Except, if there are no other versions of that package (e.g., the
first one being copied in), it produces a .mcd as if against an
"empty" package, so the .mcd is as large as the .mcz because it has
everything.

On Wed, Feb 19, 2014 at 4:12 PM, Chris Muller <[hidden email]> wrote:

On 19.02.2014, at 23:31, Chris Muller <[hidden email]> wrote:

> Another observation, every time a new package is saved, SqueakSource
> produces a .mcd diff with its ancestor.
>

IIRC this is not every-time a package is saved but when the mcd is actually
accessed, Either via web or via MC

> Except, if there are no other versions of that package (e.g., the
> first one being copied in), it produces a .mcd as if against an
> "empty" package, so the .mcd is as large as the .mcz because it has
> everything.

Jep.

Best
        -Tobias

On 19.02.2014, at 14:38, Tobias Pape <[hidden email]> wrote:

> On 19.02.2014, at 23:31, Chris Muller <[hidden email]> wrote:
>
>> Another observation, every time a new package is saved, SqueakSource
>> produces a .mcd diff with its ancestor.
>>
>
> IIRC this is not every-time a package is saved but when the mcd is actually
> accessed, Either via web or via MC

Correct. In the web interface it generates a name for it, but the file is created only when you click it.

>> Except, if there are no other versions of that package (e.g., the
>> first one being copied in), it produces a .mcd as if against an
>> "empty" package, so the .mcd is as large as the .mcz because it has
>> everything.
>
> Jep.

Which does not make not much sense, agreed. It's an artifact of the change set generation mechanism, the first changeset should have the complete code.

> Best
> -Tobias
>
>

- Bert -