Metacello load script won't update the configuration
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
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, 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
Yes, that is exactly what I need! Thank you!
On 14 Sep 2015, at 23:10, Dale Henrichs <dale.henrichs@gemtalksystems.com> 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, 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
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 <dale.henrichs@gemtalksystems.com> 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, 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
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 <dale.henrichs@gemtalksystems.com <mailto:dale.henrichs@gemtalksystems.com>> 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, 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
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 <dale.henrichs@gemtalksystems.com> 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:dale.henrichs@gemtalksystems.com>dale.henrichs@gemtalksystems.com <mailto:dale.henrichs@gemtalksystems.com>> 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
Unfortunately, I believe that that is the case:) FWIW, I think that they do intend to have the latest Metacello in Pharo5.0, but that apparently hasn't happened yet ... Dale On 11/23/2015 10:43 AM, Yuriy Tymchuk wrote:
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 <dale.henrichs@gemtalksystems.com <mailto:dale.henrichs@gemtalksystems.com>> 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 <dale.henrichs@gemtalksystems.com> 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, 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
On 23 Nov 2015, at 15:53, Dale Henrichs <dale.henrichs@gemtalksystems.com> wrote:
Unfortunately, I believe that that is the case:)
FWIW, I think that they do intend to have the latest Metacello in Pharo5.0, but that apparently hasn't happened yet â¦
There is an open issue. Someone has to do it and it is done. If nobody does it, it will not happen. Marcus
I did the configuration 2 months ago but was not integrated because of some critics rules failing. And some of them are not valid for a project supporting many smalltalk and many versions. I synchronized all the code and tests were green. The code is not worst as the current metacello version so I do not see why it is not integrated. ----- Marcus Denker <marcus.denker@inria.fr> a écrit :
On 23 Nov 2015, at 15:53, Dale Henrichs <dale.henrichs@gemtalksystems.com> wrote:
Unfortunately, I believe that that is the case:)
FWIW, I think that they do intend to have the latest Metacello in Pharo5.0, but that apparently hasn't happened yet â¦
There is an open issue. Someone has to do it and it is done. If nobody does it, it will not happen.
Marcus
Christophe, If there are outstanding code critic issues that _should_ be addressed, please add a fresh list (with the critical issues highlighted) to Metacello Issue #362[1] and I'll take care of them ASAP ... Dale [1] https://github.com/dalehenrich/metacello-work/issues/362 On 11/23/2015 11:25 AM, Christophe Demarey wrote:
I did the configuration 2 months ago but was not integrated because of some critics rules failing. And some of them are not valid for a project supporting many smalltalk and many versions. I synchronized all the code and tests were green. The code is not worst as the current metacello version so I do not see why it is not integrated.
----- Marcus Denker <marcus.denker@inria.fr> a écrit :
On 23 Nov 2015, at 15:53, Dale Henrichs <dale.henrichs@gemtalksystems.com> wrote:
Unfortunately, I believe that that is the case:)
FWIW, I think that they do intend to have the latest Metacello in Pharo5.0, but that apparently hasn't happened yet ⦠There is an open issue. Someone has to do it and it is done. If nobody does it, it will not happen.
Marcus
On 23 Nov 2015, at 16:25, Christophe Demarey <christophe.demarey@inria.fr> wrote:
I did the configuration 2 months ago but was not integrated because of some critics rules failing. And some of them are not valid for a project supporting many smalltalk and many versions. I synchronized all the code and tests were green. The code is not worst as the current metacello version so I do not see why it is not integrated.
because with >650 issues I do never look through all of them because an issue âWork neededâ might be ready for integration. I *only* look at issues that are âfix review neededâ or âfix reviewed by the monkeyâ. Marcus
Le 23 nov. 2015 à 20:32, Marcus Denker a écrit :
On 23 Nov 2015, at 16:25, Christophe Demarey <christophe.demarey@inria.fr> wrote:
I did the configuration 2 months ago but was not integrated because of some critics rules failing. And some of them are not valid for a project supporting many smalltalk and many versions. I synchronized all the code and tests were green. The code is not worst as the current metacello version so I do not see why it is not integrated.
because with >650 issues I do never look through all of them because an issue âWork neededâ might be ready for integration. I *only* look at issues that are âfix review neededâ or âfix reviewed by the monkeyâ.
That is easily understandable. What I meant is that Stéphane tried to integrate it (I told Stéphane that it was ready) but the integration failed and I did not get the reason back. I will try to resync (again) and provide critics feedback to Dale.
participants (5)
-
Christophe Demarey -
Christophe Demarey
-
Dale Henrichs -
Marcus Denker -
Yuriy Tymchuk