You should read the beginning of the chapter on metacello.
Metacello is a map
Monticello element of the map

You load elements by asking the map.

Stef

On Sat, May 13, 2017 at 3:43 AM, Andreas Sunardi <a.suna...@gmail.com>
wrote:

> Hi Stephane,
>
> Indeed, PetitParser installation from Catalog Browser works just fine!
> Thank you very much.
>
> I used Monticello Browser before, but not Catalog Browser. I didn't know
> this is the preferred method to install package. I don't think
> DeepIntoPharo mentions about Catalog Browser, but maybe my version is
> outdated.
>
> Thanks again, Stephane.
>
> --
> Andreas Sunardi
>
> On Fri, May 12, 2017 at 12:48 PM, Stephane Ducasse <
> stepharo.s...@gmail.com> wrote:
>
>> Sorry I meant the catalogBrowser.
>> Using the catalogBrowser on a given version of Pharo you should access
>> the configuration for this version (if people updated it correctly).
>> Our plan is to make sure that such configurations are validated.
>> Stef
>>
>> On Fri, May 12, 2017 at 9:47 PM, Stephane Ducasse <
>> stepharo.s...@gmail.com> wrote:
>>
>>> Hi andreas
>>>
>>> Normally you should be able to load a package using the
>>> ConfigurationBrowser and the configuration (now I do not know the one of
>>> PetitParser)
>>> should take care of the pharo version for you.
>>>
>>> stef
>>>
>>>
>>> On Fri, May 12, 2017 at 7:06 PM, Andreas Sunardi <a.suna...@gmail.com>
>>> wrote:
>>>
>>>> Following DeepIntoPharo, I tried to install PetitParser into my Pharo
>>>> 5.0 image (I noticed PetitParser installation problem email in March). It
>>>> failed with the message WinPlatform class was undefined. I went to Moose's
>>>> PetitParser site in smalltalkhub and followed the instruction there, and
>>>> this also failed.
>>>>
>>>> Out of frustration, I downloaded Moose 6.0 and thought I'd start from
>>>> Moose image instead. But then I noticed Moose's PetitParser package has
>>>> ConfigurationOfPetitParser from version TudorGirba.77 and the instruction I
>>>> followed was trying to install it using version TudorGirba.80. Back to my
>>>> Pharo 5 image, I unload/remove ConfigurationOfPetitParser and load version
>>>> TudorGirba.77. And this works!
>>>>
>>>> But this way to solve PetitParser installation problem seems wrong. I
>>>> figure if this could very well happen with other packages too. What is the
>>>> right way to find package version that works with my image/pharo version?
>>>> Or is this an issue with PetitParser package itself and should I ask/report
>>>> this to Moose team?
>>>>
>>>> --
>>>> Andreas Sunardi
>>>>
>>>
>>>
>>
>

Reply via email to