this is a consequence on how we do the integration: by merging packages (to 
prevent ugly overrides)... so, each time I integrate a change, it creates a new 
monticello package, who is allocated on the Pharo20 repository. 
It does not matters if the resulting package is equal to the original one (in 
fact, that what should happen most of the time)... but yes, version number and 
commiter name will change. 

Esteban


On Mar 25, 2013, at 4:56 PM, "Torsten Bergmann" <asta...@gmx.de> wrote:

> Pharo 2.0 has "NativeBoost-Core-EstebanLorenzano.116" which is in 
> http://ss3.gemstone.com/ss/Pharo20 since NB is now in Pharo 2.0
> 
> The same version is not in the old squeaksource/NativeBoost repo
> and also not in the new SmalltalkHub native boost project.
> 
> When having additions to NB where should I place them? 
> 
> 
> 


Reply via email to