YES!!!!

To create a new version from the current versions IN the repository, or LOADED 
in the image also would work.


thanks Tudor for the detailed description!

Fernando



On Feb 10, 2010, at 4:28 PM, Tudor Girba wrote:

> Hi,
> 
> Well, before you will release anything, you will want those packages  
> in your image to see if it works.
> 
> To get the latest versions of all packages from a configuration, just  
> load a baseline and if there are no hardcoded versions in it, you get  
> the latest code. Afterwards, you just create a new version from that  
> baseline.
> 
> Is that not the use case?
> 
> Cheers,
> Doru
> 
> On 10 Feb 2010, at 16:24, Mariano Martinez Peck wrote:
> 
>> 
>> 
>> On Wed, Feb 10, 2010 at 4:21 PM, Tudor Girba <[email protected]>  
>> wrote:
>> Hi,
>> 
>> You get this behavior in Spawn New Version in the OB-Metacello and in
>> GTMetaceller.
>> 
>> To run GTMetaceller you have to have Metacello 1.0-beta.23. To get it:
>> 
>> Gofer new
>>       squeaksource: 'glamoroust';
>>       package: 'ConfigurationOfGlamoroust';
>>       load.
>> (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault.
>> (Smalltalk at: #GTMetaceller) perform: #open
>> 
>> 
>> Tudor: I think there is a little different. We wanted the last  
>> version that is in the repository (if I understood ok), but the  
>> spawn says "The package specs for the new method reflect the  
>> currently loaded Monticello package versions"  So....he has to load  
>> first all the last versions ?
>> 
>> 
>> 
>> Cheers,
>> Doru
>> 
>> 
>> On 10 Feb 2010, at 15:54, Mariano Martinez Peck wrote:
>> 
>>> 
>>> 
>>> On Wed, Feb 10, 2010 at 3:49 PM, Fernando olivero <[email protected]
>>>> wrote:
>>> Hi, is this feature available in Metacello?
>>> 
>>> To create a new version automatically by
>>>       1.  using latest version number found in any method + 1 , in
>>> the ConfigurationOfXXX)
>>>       2. using commited packages in the repository
>>> 
>>> Something like
>>> 
>>> ConfigurationOfXXX>>createVersionNamed: aVersionNameSelector
>>> 
>>> 
>>> That would compile the method
>>>       ConfigurationOfXXX>>aVersionNameSelector
>>>               <version: 'lastestVersion+1' imports: #('1.0-
>>> baseline')>
>>>       spec for: .... do: [
>>>               spec blessing: #development.
>>>               spec repository: 'http://www.squeaksource.com/XXX'.
>>>               spec
>>>                       author:'Me';
>>>                       package: 'Gaucho-Core' with: 'Gaucho-Core-
>>> FernandoOlivero.78' ;
>>>                       package: 'Gaucho-Drawables' with:'Gaucho-
>>> Drawables-FernandoOlivero.37' ;
>>>                       .....
>>> 
>>> Or everybody is creating new version by hand, fetching the latest
>>> versions names from the monticello repo?
>>> 
>>> I am doing exactly that. But that's because I don't like and I don't
>>> trust in automagic ;)
>>> 
>>> Anyway, I think that the Metacello-OB tools may help you there. I am
>>> not sure as I don't use such tools, but maybe there is something.
>>> You should take a look or wait for other responses ;)
>>> 
>>> Check: http://code.google.com/p/metacello/wiki/MetacelloTools
>>> 
>>> Cheers
>>> 
>>> Mariano
>>> 
>>> 
>>> 
>>> Thanks,
>>> Fernando
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>> 
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> --
>> www.tudorgirba.com
>> 
>> "It's not how it is, it is how we see it."
>> 
>> 
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> --
> www.tudorgirba.com
> 
> "Problem solving efficiency grows with the abstractness level of  
> problem understanding."
> 
> 
> 
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to