question about MetacelloToolBox
Locked
question about MetacelloToolBox
 
|
Hi Dale. I have ConfigurationOfFuel loaded in my image where last version is 1.7 (which is #release).
Now I wanted to experiment and I have evaluated: MetacelloToolBox createDevelopment: '1.10' for: 'Fuel' importFromBaseline: '1.8-baseline' description: 'new version'. And I have a problem...in baseline 1.8 I have a part that looks like this: --------- spec for: #'pharo1.3.x' do: [ spec package: 'FuelCompatibilityBeforePharo14' with: [ spec requires: #( 'Fuel' )]. spec group: 'Core' with: #('FuelCompatibilityBeforePharo14'). ]. spec for: #'pharo1.2.x' do: [ spec package: 'FuelCompatibilityBeforePharo13' with: [ spec requires: #( 'FuelCompatibilityBeforePharo14' )]. spec group: 'Core' with: #('FuelCompatibilityBeforePharo13'). ]. spec for: #'pharo1.1.x' do: [ spec package: 'FuelCompatibilityBeforePharo12' with: [ spec requires: #( 'FuelCompatibilityBeforePharo13' )]. spec group: 'Core' with: #('FuelCompatibilityBeforePharo12'). ]. spec for: #squeak do: [ spec package: 'FuelCompatibilityBeforePharo12'; package: 'FuelCompatibilityForSqueak'. spec group: 'Core' with: #('FuelCompatibilityBeforePharo12' 'FuelCompatibilityForSqueak'). ]. ----------- And in the generated version, the associated part looks like this: spec for: #'pharo1.3.x' do: [ spec package: 'FuelCompatibilityBeforePharo14' with: 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. spec for: #'pharo1.2.x' do: [ spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. spec for: #'pharo1.1.x' do: [ spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. spec for: #'squeak' do: [ spec package: 'FuelCompatibilityBeforePharo12' with: ''; package: 'FuelCompatibilityForSqueak' with: ''. ]. ------ notice the empty strings for the versions.... First I note that I didn't have those packages loaded in my image, because, obviously I was in a Pharo 1.3 so I didn't need them (well, only FuelCompatibilityBeforePharo14 which in fact was the ont which did work). But then I have download all those packages and still got the same results. Now, my question is, I should have ALL the packages of the conf in order to work? but in such a case then I am screw because I cannot load them becaue since they are "compatibility" packages they have overrides in Fuel itself. So Fuel package will be dirty. Would metacello took the dirty version or the exact mcz file that I have? It is not a big problem since I can add them by hand, but I was just wondering... Thanks! -- Mariano http://marianopeck.wordpress.com |
Re: question about MetacelloToolBox
|
|
Another problem is that for that new created version, it puts: spec blessing: #'baseline'. which I think it is incorrect because it is a version. It should #development I guess.
Cheers
On Sun, Dec 11, 2011 at 4:50 PM, Mariano Martinez Peck <[hidden email]> wrote: Hi Dale. I have ConfigurationOfFuel loaded in my image where last version is 1.7 (which is #release). -- Mariano http://marianopeck.wordpress.com |
Re: question about MetacelloToolBox
|
|
Sorry, my questions are arising at differnt moments haha. In addition, shouldn't version 1.8 (the created one) include the attributes:
spec description: 'new version'. spec author: 'MarianoMartinezPeck'. spec timestamp: '11/12/2011 12:29'. ? because they are not being generated. The whole verion looks like this: version110: spec <version: '1.10' imports: #('1.8-baseline' )> spec for: #'squeakCommon' do: [ spec blessing: #'baseline'. spec package: 'Fuel' with: 'Fuel-MarianoMartinezPeck.511'; package: 'FuelTests' with: 'FuelTests-MarianoMartinezPeck.188'; package: 'FuelProgressUpdate' with: 'FuelProgressUpdate-MarianoMartinezPeck.30'; package: 'FuelContainer' with: 'FuelContainer'; package: 'FuelBenchmarks' with: 'FuelBenchmarks-MarianoMartinezPeck.99'; package: 'FuelLogo' with: 'FuelLogo-MartinDias.2'; package: 'FuelCompression' with: 'FuelCompression-MarianoMartinezPeck.1'; package: 'FuelExamples' with: 'FuelExamples-MartinDias.5'. ]. spec for: #'pharo' do: [ spec project: 'MagmaBase' ; project: 'SIXX' ; project: 'StOMP' . spec package: 'FuelBenchmarksMagma' with: 'FuelBenchmarksMagma'; package: 'FuelBenchmarksSIXX' with: 'FuelBenchmarksSIXX'; package: 'FuelBenchmarksStomp' with: 'FuelBenchmarksStomp'; package: 'FuelProgressUpdateBenchmarks' with: 'FuelProgressUpdateBenchmarks-MartinDias.7'; package: 'FuelBenchmarksSRP' with: 'FuelBenchmarksSRP'; package: 'FuelBenchmarksEsAndEm' with: 'FuelBenchmarksEsAndEm'; package: 'FuelPackageLoader' with: 'FuelPackageLoader-MarianoMartinezPeck.49'; package: 'FuelPackageLoaderTests' with: 'FuelPackageLoaderTests-MarianoMartinezPeck.7'; package: 'FuelMetalevel' with: 'FuelMetalevel-MarianoMartinezPeck.6'; package: 'FuelMetalevelTests' with: 'FuelMetalevelTests-MarianoMartinezPeck.6'; package: 'SRP' with: 'SRP'; package: 'EsAndEm' with: 'EsAndEm'. ]. spec for: #'pharo1.3.x' do: [ spec package: 'FuelCompatibilityBeforePharo14' with: 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. spec for: #'pharo1.2.x' do: [ spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. spec for: #'pharo1.1.x' do: [ spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. spec for: #'squeak' do: [ spec package: 'FuelCompatibilityBeforePharo12' with: ''; package: 'FuelCompatibilityForSqueak' with: ''. ]. THanks On Sun, Dec 11, 2011 at 8:29 PM, Mariano Martinez Peck <[hidden email]> wrote: Another problem is that for that new created version, it puts: spec blessing: #'baseline'. which I think it is incorrect because it is a version. It should #development I guess. -- Mariano http://marianopeck.wordpress.com |
Re: question about MetacelloToolBox
|
|
In reply to this post by Mariano Martinez Peck
Mariano,
You have entered the 'unfinished' part of the toolbox. At this point in time I'm not really sure what we can do about sections for other platforms. If I'm not mistaken, that version should not validate clean, so at least we have the ability to flag a configuration as unfinished ... I am open to ideas. Dale ----- Original Message ----- | From: "Mariano Martinez Peck" <[hidden email]> | To: [hidden email] | Sent: Sunday, December 11, 2011 7:50:55 AM | Subject: [Metacello] question about MetacelloToolBox | | Hi Dale. I have ConfigurationOfFuel loaded in my image where last | version is 1.7 (which is #release). | | Now I wanted to experiment and I have evaluated: | | | MetacelloToolBox | createDevelopment: '1.10' | for: 'Fuel' | importFromBaseline: '1.8-baseline' | description: 'new version'. | | | And I have a problem...in baseline 1.8 I have a part that looks like | this: | | | --------- | | spec for: #'pharo1.3.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo14' with: [ | spec requires: #( 'Fuel' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo14'). | | ]. | | | | spec for: #'pharo1.2.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo13' with: [ | spec requires: #( 'FuelCompatibilityBeforePharo14' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo13'). | | ]. | | spec for: #'pharo1.1.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo12' with: [ | spec requires: #( 'FuelCompatibilityBeforePharo13' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12'). | | ]. | | | spec for: #squeak do: [ | | spec | package: 'FuelCompatibilityBeforePharo12'; | package: 'FuelCompatibilityForSqueak'. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12' | 'FuelCompatibilityForSqueak'). | | ]. | | ----------- | | | And in the generated version, the associated part looks like this: | | | spec for: #'pharo1.3.x' do: [ | spec package: 'FuelCompatibilityBeforePharo14' with: | 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. | | spec for: #'pharo1.2.x' do: [ | spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. | | spec for: #'pharo1.1.x' do: [ | spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. | | spec for: #'squeak' do: [ | spec | package: 'FuelCompatibilityBeforePharo12' with: ''; | package: 'FuelCompatibilityForSqueak' with: ''. ]. | | | ------ | | notice the empty strings for the versions.... | First I note that I didn't have those packages loaded in my image, | because, obviously I was in a Pharo 1.3 so I didn't need them (well, | only FuelCompatibilityBeforePharo14 which in fact was the ont which | did work). | But then I have download all those packages and still got the same | results. | Now, my question is, I should have ALL the packages of the conf in | order to work? but in such a case then I am screw because I cannot | load them becaue since they are "compatibility" packages they have | overrides in Fuel itself. So Fuel package will be dirty. Would | metacello took the dirty version or the exact mcz file that I have? | It is not a big problem since I can add them by hand, but I was just | wondering... | | Thanks! | | -- | Mariano | http://marianopeck.wordpress.com | | |
Re: question about MetacelloToolBox
|
|
In reply to this post by Mariano Martinez Peck
Mariano,
This sounds like a bug, but there is an explicit test for this in MetacelloDevelopmentCycleTutorialTests>>testCreateDevelopment that checks for the #blessing: being #development, so there must be something slightly different in your case so I'd like to get to the bottom of this one ... If you run the test yourself, put a halt at the end of the #testCreateDevelopment method so you can look at the baseline in ConfigurationOfMetacello_Dev_Cycle. I'd like to try to understand the differences that might lead to the bug ... Alternatively you could send me your baseline and I could take a look myself. Dale ----- Original Message ----- | From: "Mariano Martinez Peck" <[hidden email]> | To: [hidden email] | Sent: Sunday, December 11, 2011 11:29:18 AM | Subject: [Metacello] Re: question about MetacelloToolBox | | Another problem is that for that new created version, it puts: spec | blessing: #'baseline'. which I think it is incorrect because it is a | version. It should #development I guess. | | Cheers | | | On Sun, Dec 11, 2011 at 4:50 PM, Mariano Martinez Peck < | [hidden email] > wrote: | | | Hi Dale. I have ConfigurationOfFuel loaded in my image where last | version is 1.7 (which is #release). | | Now I wanted to experiment and I have evaluated: | | | MetacelloToolBox | createDevelopment: '1.10' | for: 'Fuel' | importFromBaseline: '1.8-baseline' | description: 'new version'. | | | And I have a problem...in baseline 1.8 I have a part that looks like | this: | | | --------- | | spec for: #'pharo1.3.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo14' with: [ | spec requires: #( 'Fuel' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo14'). | | ]. | | | | spec for: #'pharo1.2.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo13' with: [ | spec requires: #( 'FuelCompatibilityBeforePharo14' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo13'). | | ]. | | spec for: #'pharo1.1.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo12' with: [ | spec requires: #( 'FuelCompatibilityBeforePharo13' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12'). | | ]. | | | spec for: #squeak do: [ | | spec | package: 'FuelCompatibilityBeforePharo12'; | package: 'FuelCompatibilityForSqueak'. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12' | 'FuelCompatibilityForSqueak'). | | ]. | | ----------- | | | And in the generated version, the associated part looks like this: | | | spec for: #'pharo1.3.x' do: [ | spec package: 'FuelCompatibilityBeforePharo14' with: | 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. | | spec for: #'pharo1.2.x' do: [ | spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. | | spec for: #'pharo1.1.x' do: [ | spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. | | spec for: #'squeak' do: [ | spec | package: 'FuelCompatibilityBeforePharo12' with: ''; | package: 'FuelCompatibilityForSqueak' with: ''. ]. | | | ------ | | notice the empty strings for the versions.... | First I note that I didn't have those packages loaded in my image, | because, obviously I was in a Pharo 1.3 so I didn't need them (well, | only FuelCompatibilityBeforePharo14 which in fact was the ont which | did work). | But then I have download all those packages and still got the same | results. | Now, my question is, I should have ALL the packages of the conf in | order to work? but in such a case then I am screw because I cannot | load them becaue since they are "compatibility" packages they have | overrides in Fuel itself. So Fuel package will be dirty. Would | metacello took the dirty version or the exact mcz file that I have? | It is not a big problem since I can add them by hand, but I was just | wondering... | | Thanks! | | -- | Mariano | http://marianopeck.wordpress.com | | | | | -- | Mariano | http://marianopeck.wordpress.com | | |
Re: question about MetacelloToolBox
|
|
In reply to this post by Mariano Martinez Peck
Mariano,
Hmmm, this is also tested in MetacelloDevelopmentCycleTutorialTests>>testCreateDevelopment... Ahhh, I see the problem, you have no #common section in your baseline, and the toolbox isn't adding the #common section, which is where the baseline/description/author/timestamp are normall inserted... ...also for the other sections #squeakCommon and #pharo, the blessings are not checked and the #baseline sneaks through ... I'll submit a bug on this .... still not sure what to do about the empty strings for packages that we have no info on, but at least we can fix up these problems ... Dale ----- Original Message ----- | From: "Mariano Martinez Peck" <[hidden email]> | To: [hidden email] | Sent: Sunday, December 11, 2011 11:32:26 AM | Subject: [Metacello] Re: question about MetacelloToolBox | | Sorry, my questions are arising at differnt moments haha. In | addition, shouldn't version 1.8 (the created one) include the | attributes: | | spec description: 'new version'. | spec author: 'MarianoMartinezPeck'. | spec timestamp: '11/12/2011 12:29'. | | ? because they are not being generated. The whole verion looks like | this: | | | version110: spec | <version: '1.10' imports: #('1.8-baseline' )> | | spec for: #'squeakCommon' do: [ | spec blessing: #'baseline'. | spec | package: 'Fuel' with: 'Fuel-MarianoMartinezPeck.511'; | package: 'FuelTests' with: 'FuelTests-MarianoMartinezPeck.188'; | package: 'FuelProgressUpdate' with: | 'FuelProgressUpdate-MarianoMartinezPeck.30'; | package: 'FuelContainer' with: 'FuelContainer'; | package: 'FuelBenchmarks' with: | 'FuelBenchmarks-MarianoMartinezPeck.99'; | package: 'FuelLogo' with: 'FuelLogo-MartinDias.2'; | package: 'FuelCompression' with: | 'FuelCompression-MarianoMartinezPeck.1'; | package: 'FuelExamples' with: 'FuelExamples-MartinDias.5'. ]. | | spec for: #'pharo' do: [ | spec | project: 'MagmaBase' ; | project: 'SIXX' ; | project: 'StOMP' . | spec | package: 'FuelBenchmarksMagma' with: 'FuelBenchmarksMagma'; | package: 'FuelBenchmarksSIXX' with: 'FuelBenchmarksSIXX'; | package: 'FuelBenchmarksStomp' with: 'FuelBenchmarksStomp'; | package: 'FuelProgressUpdateBenchmarks' with: | 'FuelProgressUpdateBenchmarks-MartinDias.7'; | package: 'FuelBenchmarksSRP' with: 'FuelBenchmarksSRP'; | package: 'FuelBenchmarksEsAndEm' with: 'FuelBenchmarksEsAndEm'; | package: 'FuelPackageLoader' with: | 'FuelPackageLoader-MarianoMartinezPeck.49'; | package: 'FuelPackageLoaderTests' with: | 'FuelPackageLoaderTests-MarianoMartinezPeck.7'; | package: 'FuelMetalevel' with: 'FuelMetalevel-MarianoMartinezPeck.6'; | package: 'FuelMetalevelTests' with: | 'FuelMetalevelTests-MarianoMartinezPeck.6'; | package: 'SRP' with: 'SRP'; | package: 'EsAndEm' with: 'EsAndEm'. ]. | | spec for: #'pharo1.3.x' do: [ | spec package: 'FuelCompatibilityBeforePharo14' with: | 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. | | spec for: #'pharo1.2.x' do: [ | spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. | | spec for: #'pharo1.1.x' do: [ | spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. | | spec for: #'squeak' do: [ | spec | package: 'FuelCompatibilityBeforePharo12' with: ''; | package: 'FuelCompatibilityForSqueak' with: ''. ]. | | | | THanks | | | | On Sun, Dec 11, 2011 at 8:29 PM, Mariano Martinez Peck < | [hidden email] > wrote: | | | Another problem is that for that new created version, it puts: spec | blessing: #'baseline'. which I think it is incorrect because it is a | version. It should #development I guess. | | Cheers | | | | | On Sun, Dec 11, 2011 at 4:50 PM, Mariano Martinez Peck < | [hidden email] > wrote: | | | Hi Dale. I have ConfigurationOfFuel loaded in my image where last | version is 1.7 (which is #release). | | Now I wanted to experiment and I have evaluated: | | | MetacelloToolBox | createDevelopment: '1.10' | for: 'Fuel' | importFromBaseline: '1.8-baseline' | description: 'new version'. | | | And I have a problem...in baseline 1.8 I have a part that looks like | this: | | | --------- | | spec for: #'pharo1.3.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo14' with: [ | spec requires: #( 'Fuel' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo14'). | | ]. | | | | spec for: #'pharo1.2.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo13' with: [ | spec requires: #( 'FuelCompatibilityBeforePharo14' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo13'). | | ]. | | spec for: #'pharo1.1.x' do: [ | | spec | package: 'FuelCompatibilityBeforePharo12' with: [ | spec requires: #( 'FuelCompatibilityBeforePharo13' )]. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12'). | | ]. | | | spec for: #squeak do: [ | | spec | package: 'FuelCompatibilityBeforePharo12'; | package: 'FuelCompatibilityForSqueak'. | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12' | 'FuelCompatibilityForSqueak'). | | ]. | | ----------- | | | And in the generated version, the associated part looks like this: | | | spec for: #'pharo1.3.x' do: [ | spec package: 'FuelCompatibilityBeforePharo14' with: | 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. | | spec for: #'pharo1.2.x' do: [ | spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. | | spec for: #'pharo1.1.x' do: [ | spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. | | spec for: #'squeak' do: [ | spec | package: 'FuelCompatibilityBeforePharo12' with: ''; | package: 'FuelCompatibilityForSqueak' with: ''. ]. | | | ------ | | notice the empty strings for the versions.... | First I note that I didn't have those packages loaded in my image, | because, obviously I was in a Pharo 1.3 so I didn't need them (well, | only FuelCompatibilityBeforePharo14 which in fact was the ont which | did work). | But then I have download all those packages and still got the same | results. | Now, my question is, I should have ALL the packages of the conf in | order to work? but in such a case then I am screw because I cannot | load them becaue since they are "compatibility" packages they have | overrides in Fuel itself. So Fuel package will be dirty. Would | metacello took the dirty version or the exact mcz file that I have? | It is not a big problem since I can add them by hand, but I was just | wondering... | | Thanks! | | -- | Mariano | http://marianopeck.wordpress.com | | | | | -- | Mariano | http://marianopeck.wordpress.com | | | | | -- | Mariano | http://marianopeck.wordpress.com | | |
Re: question about MetacelloToolBox
|
|
On Mon, Dec 12, 2011 at 6:40 PM, Dale Henrichs <[hidden email]> wrote: Mariano, Sorry Dale I just read the emails. It seems you have just found it, but in any case, I was using the ConfigurationOfFuel in http://ss3.gemstone.com/ss/Fuel and I was doing: MetacelloToolBox createDevelopment: '1.10' for: 'Fuel' importFromBaseline: '1.8-baseline' description: 'new version'. I'll submit a bug on this .... still not sure what to do about the empty strings for packages that we have no info on, What do you mean "no info on" ? because I had the same problem even explcitly downloading those packages (even if I didn't need them in that current image I was using) but at least we can fix up these problems ... Thanks :)
-- Mariano http://marianopeck.wordpress.com |
Re: question about MetacelloToolBox
|
|
Mariano,
The "no info on" comment refers to packages or projects that aren't loaded into the current image ... the "no info" also refers to sections that don't relate to the current image, like #gemstone or #squeak or a different version of pharo Dale ----- Original Message ----- | From: "Mariano Martinez Peck" <[hidden email]> | To: [hidden email] | Sent: Monday, December 12, 2011 2:07:40 PM | Subject: Re: [Metacello] Re: question about MetacelloToolBox | | | | | On Mon, Dec 12, 2011 at 6:40 PM, Dale Henrichs < [hidden email] | > wrote: | | | Mariano, | | Hmmm, this is also tested in | MetacelloDevelopmentCycleTutorialTests>>testCreateDevelopment... | | Ahhh, I see the problem, you have no #common section in your | baseline, and the toolbox isn't adding the #common section, which is | where the baseline/description/author/timestamp are normall | inserted... | | ...also for the other sections #squeakCommon and #pharo, the | blessings are not checked and the #baseline sneaks through ... | | | | Sorry Dale I just read the emails. It seems you have just found it, | but in any case, I was using the ConfigurationOfFuel in | http://ss3.gemstone.com/ss/Fuel | and I was doing: | | MetacelloToolBox | createDevelopment: '1.10' | for: 'Fuel' | importFromBaseline: '1.8-baseline' | description: 'new version'. | | | | | | I'll submit a bug on this .... still not sure what to do about the | empty strings for packages that we have no info on, | | What do you mean "no info on" ? because I had the same problem even | explcitly downloading those packages (even if I didn't need them in | that current image I was using) | | | | | but at least we can fix up these problems ... | | | | | Thanks :) | | | | Dale | | ----- Original Message ----- | | From: "Mariano Martinez Peck" < [hidden email] > | | To: [hidden email] | | | Sent: Sunday, December 11, 2011 11:32:26 AM | | Subject: [Metacello] Re: question about MetacelloToolBox | | | | | | Sorry, my questions are arising at differnt moments haha. In | | addition, shouldn't version 1.8 (the created one) include the | | attributes: | | | | spec description: 'new version'. | | spec author: 'MarianoMartinezPeck'. | | spec timestamp: '11/12/2011 12:29'. | | | | ? because they are not being generated. The whole verion looks like | | this: | | | | | | version110: spec | | <version: '1.10' imports: #('1.8-baseline' )> | | | | spec for: #'squeakCommon' do: [ | | spec blessing: #'baseline'. | | spec | | package: 'Fuel' with: 'Fuel-MarianoMartinezPeck.511'; | | package: 'FuelTests' with: 'FuelTests-MarianoMartinezPeck.188'; | | package: 'FuelProgressUpdate' with: | | 'FuelProgressUpdate-MarianoMartinezPeck.30'; | | package: 'FuelContainer' with: 'FuelContainer'; | | package: 'FuelBenchmarks' with: | | 'FuelBenchmarks-MarianoMartinezPeck.99'; | | package: 'FuelLogo' with: 'FuelLogo-MartinDias.2'; | | package: 'FuelCompression' with: | | 'FuelCompression-MarianoMartinezPeck.1'; | | package: 'FuelExamples' with: 'FuelExamples-MartinDias.5'. ]. | | | | spec for: #'pharo' do: [ | | spec | | project: 'MagmaBase' ; | | project: 'SIXX' ; | | project: 'StOMP' . | | spec | | package: 'FuelBenchmarksMagma' with: 'FuelBenchmarksMagma'; | | package: 'FuelBenchmarksSIXX' with: 'FuelBenchmarksSIXX'; | | package: 'FuelBenchmarksStomp' with: 'FuelBenchmarksStomp'; | | package: 'FuelProgressUpdateBenchmarks' with: | | 'FuelProgressUpdateBenchmarks-MartinDias.7'; | | package: 'FuelBenchmarksSRP' with: 'FuelBenchmarksSRP'; | | package: 'FuelBenchmarksEsAndEm' with: 'FuelBenchmarksEsAndEm'; | | package: 'FuelPackageLoader' with: | | 'FuelPackageLoader-MarianoMartinezPeck.49'; | | package: 'FuelPackageLoaderTests' with: | | 'FuelPackageLoaderTests-MarianoMartinezPeck.7'; | | package: 'FuelMetalevel' with: | | 'FuelMetalevel-MarianoMartinezPeck.6'; | | package: 'FuelMetalevelTests' with: | | 'FuelMetalevelTests-MarianoMartinezPeck.6'; | | package: 'SRP' with: 'SRP'; | | package: 'EsAndEm' with: 'EsAndEm'. ]. | | | | spec for: #'pharo1.3.x' do: [ | | spec package: 'FuelCompatibilityBeforePharo14' with: | | 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. | | | | spec for: #'pharo1.2.x' do: [ | | spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. | | | | spec for: #'pharo1.1.x' do: [ | | spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. | | | | spec for: #'squeak' do: [ | | spec | | package: 'FuelCompatibilityBeforePharo12' with: ''; | | package: 'FuelCompatibilityForSqueak' with: ''. ]. | | | | | | | | THanks | | | | | | | | On Sun, Dec 11, 2011 at 8:29 PM, Mariano Martinez Peck < | | [hidden email] > wrote: | | | | | | Another problem is that for that new created version, it puts: spec | | blessing: #'baseline'. which I think it is incorrect because it is | | a | | version. It should #development I guess. | | | | Cheers | | | | | | | | | | On Sun, Dec 11, 2011 at 4:50 PM, Mariano Martinez Peck < | | [hidden email] > wrote: | | | | | | Hi Dale. I have ConfigurationOfFuel loaded in my image where last | | version is 1.7 (which is #release). | | | | Now I wanted to experiment and I have evaluated: | | | | | | MetacelloToolBox | | createDevelopment: '1.10' | | for: 'Fuel' | | importFromBaseline: '1.8-baseline' | | description: 'new version'. | | | | | | And I have a problem...in baseline 1.8 I have a part that looks | | like | | this: | | | | | | --------- | | | | spec for: #'pharo1.3.x' do: [ | | | | spec | | package: 'FuelCompatibilityBeforePharo14' with: [ | | spec requires: #( 'Fuel' )]. | | | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo14'). | | | | ]. | | | | | | | | spec for: #'pharo1.2.x' do: [ | | | | spec | | package: 'FuelCompatibilityBeforePharo13' with: [ | | spec requires: #( 'FuelCompatibilityBeforePharo14' )]. | | | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo13'). | | | | ]. | | | | spec for: #'pharo1.1.x' do: [ | | | | spec | | package: 'FuelCompatibilityBeforePharo12' with: [ | | spec requires: #( 'FuelCompatibilityBeforePharo13' )]. | | | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12'). | | | | ]. | | | | | | spec for: #squeak do: [ | | | | spec | | package: 'FuelCompatibilityBeforePharo12'; | | package: 'FuelCompatibilityForSqueak'. | | | | spec group: 'Core' with: #('FuelCompatibilityBeforePharo12' | | 'FuelCompatibilityForSqueak'). | | | | ]. | | | | ----------- | | | | | | And in the generated version, the associated part looks like this: | | | | | | spec for: #'pharo1.3.x' do: [ | | spec package: 'FuelCompatibilityBeforePharo14' with: | | 'FuelCompatibilityBeforePharo14-MarianoMartinezPeck.1'. ]. | | | | spec for: #'pharo1.2.x' do: [ | | spec package: 'FuelCompatibilityBeforePharo13' with: ''. ]. | | | | spec for: #'pharo1.1.x' do: [ | | spec package: 'FuelCompatibilityBeforePharo12' with: ''. ]. | | | | spec for: #'squeak' do: [ | | spec | | package: 'FuelCompatibilityBeforePharo12' with: ''; | | package: 'FuelCompatibilityForSqueak' with: ''. ]. | | | | | | ------ | | | | notice the empty strings for the versions.... | | First I note that I didn't have those packages loaded in my image, | | because, obviously I was in a Pharo 1.3 so I didn't need them | | (well, | | only FuelCompatibilityBeforePharo14 which in fact was the ont which | | did work). | | But then I have download all those packages and still got the same | | results. | | Now, my question is, I should have ALL the packages of the conf in | | order to work? but in such a case then I am screw because I cannot | | load them becaue since they are "compatibility" packages they have | | overrides in Fuel itself. So Fuel package will be dirty. Would | | metacello took the dirty version or the exact mcz file that I have? | | It is not a big problem since I can add them by hand, but I was | | just | | wondering... | | | | Thanks! | | | | -- | | Mariano | | http://marianopeck.wordpress.com | | | | | | | | | | -- | | Mariano | | http://marianopeck.wordpress.com | | | | | | | | | | -- | | Mariano | | http://marianopeck.wordpress.com | | | | | | | | -- | Mariano | http://marianopeck.wordpress.com | | |
«
Return to Metacello
|
1 view|%1 views
| Free forum by Nabble | Edit this page |