loading Metacello

> Hi,
>
> I'm trying to load Metacello with ConfigurationOfMetacello on a
> 2.4.4.3 extent0.seaside.dbf. When I load it using topaz, it fails with
> "No method was found for the selector
> #'bypassGoferLoadUpdateCategories' when sent to
> aMetacelloGemStonePlatform". I discovered that this is because the
> class MCPlatformSupport has a class var called Current, that is not
> migrated yet, and version 1 does not have such a method. I've tried to
> make sure that autoMigrate is on when I load this, but it does not
> seem to help.
>
> The strategy I'm following is to start with the shipped seaside
> extent, assuming that Metacello is loaded there. Then to load
> Metacello, but from a local cached repository. I can be missing
> something; is this strategy OK?
>
> Thanks
> Otto

> Otto,
>
> Your strategy should work, but sometimes there can be glitches when trying to load Metacello using Metacello...
>
> If I'm not mistaken, out of the box the 2.4.4.3 seaside extent has GLASS 1.0-beta.8.1 installed ... I don't have a 2.4.4.3 extent handy, but I just tried the following on a 2.4.4.1 seaside extent with no problems:
>
>  ConfigurationOfMetacello project updateProject.
>  ConfigurationOfMetacello project latestVersion load
>
> What version of Metacello are loading from the cached repository and what version of Metacello are you starting with?
>
> The #'bypassGoferLoadUpdateCategories'  sounds familiar to me and certainly does seem to be a migration-related issue, I'd like to be able to reproduce this so I can figure it out ...
>
> In development I resort to loading the raw Metacello mcz packages when I hit load issues: Metacello-Core, Metacello-MC, and Metacello-Platform.gemstone, so as a workaround you can do the same.
>
> In the longer term I am aiming to do some sort of 'atomic install' so that the installer can install a new version of itself without problems ...
>
> Dale
>
> On Feb 5, 2011, at 10:25 AM, Otto Behrens wrote:
>
>> Hi,
>>
>> I'm trying to load Metacello with ConfigurationOfMetacello on a
>> 2.4.4.3 extent0.seaside.dbf. When I load it using topaz, it fails with
>> "No method was found for the selector
>> #'bypassGoferLoadUpdateCategories' when sent to
>> aMetacelloGemStonePlatform". I discovered that this is because the
>> class MCPlatformSupport has a class var called Current, that is not
>> migrated yet, and version 1 does not have such a method. I've tried to
>> make sure that autoMigrate is on when I load this, but it does not
>> seem to help.
>>
>> The strategy I'm following is to start with the shipped seaside
>> extent, assuming that Metacello is loaded there. Then to load
>> Metacello, but from a local cached repository. I can be missing
>> something; is this strategy OK?
>>
>> Thanks
>> Otto
>
>

> Hi,
>
> I'm trying to load Metacello with ConfigurationOfMetacello on a
> 2.4.4.3 extent0.seaside.dbf. When I load it using topaz, it fails with
> "No method was found for the selector
> #'bypassGoferLoadUpdateCategories' when sent to
> aMetacelloGemStonePlatform". I discovered that this is because the
> class MCPlatformSupport has a class var called Current, that is not
> migrated yet, and version 1 does not have such a method. I've tried to
> make sure that autoMigrate is on when I load this, but it does not
> seem to help.
>
> The strategy I'm following is to start with the shipped seaside
> extent, assuming that Metacello is loaded there. Then to load
> Metacello, but from a local cached repository. I can be missing
> something; is this strategy OK?
>
> Thanks
> Otto