Then this means that the latest version of Metacello is not in Pharo5 :(. I’m 
trying to make it possible for people to load the project on out of the box 
pharo.

Cheers.
Uko

> On 23 Nov 2015, at 19:20, Dale Henrichs <[email protected]> 
> wrote:
> 
> That is because you aren't using the latest version of Metacello .... one of 
> the "recent changes" (in the last year) was to allow the "chaining" of the 
> primary commands like get and load ...
> 
> Dale
> 
> On 11/23/2015 03:04 AM, Yuriy Tymchuk wrote:
>> Hi,
>> 
>> when I’m trying to do this now, adding a `get` command causes “project, 
>> baseline, or configuration not specified” error. Is it a but in metacello, 
>> or the API changed?
>> 
>> Cheers.
>> Uko
>> 
>>> On 14 Sep 2015, at 23:10, Dale Henrichs < 
>>> <mailto:[email protected]>[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> Uko,
>>> 
>>> The `get` command is used to load a fresh copy of the ConfigurationOf or 
>>> BaselineOf so the following should do the trick:
>>> 
>>> Metacello new
>>>   smalltalkhubUser: 'Pharo'
>>>   project: 'MetaRepoForPharo40';
>>>   configuration: 'QualityAssistant';
>>>   get;
>>>   load
>>> 
>>> 
>>> I make the loading of the BaselineOf and ConfigurationOf explicit so that 
>>> the developer can control when and if they want a new copy of the 
>>> BaselineOf or ConfigurationOf. 
>>> 
>>> For github urls like github://project/user/project 
>>> <github://project/user/project>, the `get` command causes the system to 
>>> invalidate the cache directory so that on the next load, the github cache 
>>> for the project is freshly downloaded so that you get the latest version of 
>>> the BaselineOf ...
>>> 
>>> Dale
>>> 
>>> On 09/14/2015 01:49 PM, Yuriy Tymchuk wrote:
>>>> Hi,
>>>> 
>>>> when you use a script like 
>>>> 
>>>> Metacello new
>>>>   smalltalkhubUser: 'Pharo'
>>>>   project: 'MetaRepoForPharo40';
>>>>   configuration: 'QualityAssistant';
>>>>   load
>>>> 
>>>> and you already have the configuration package loaded, the script is not 
>>>> updating the configuration itself. As the result you cannot update to a 
>>>> newer version. Is there a special expression that has to be used to update 
>>>> the configuration package? If not, maybe it does make sense to update the 
>>>> configuration before loading it?
>>>> 
>>>> Cheers!
>>>> Uko
>>> 
>> 
> 

Reply via email to