Versionner does not work in Pharo 2.0, and this is the main issue.
The easy turnaround is to develop in Pharo 2.0, and save the application using Pharo 1.4. But Pharo 1.4 does not know much about SmalltalkHub (e.g., "Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal'; package: 'ConfigurationOfRoassal'; load." does not work).
Christophe just told me that a SmalltalkHub repository can be used as a http monticello repository. I will try this on some point...
Cheers, Alexandre
On Mar 28, 2013, at 12:17 AM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
I do not follow your reasoning. What is the actual problem with Pharo 2.0, and why is SmalltalkHub an issue?
Cheers, Doru
On Mar 27, 2013, at 10:19 PM, Alexandre Bergel alexandre.bergel@me.com wrote:
Hi!
Roassal is now in SmalltalkHub. Although this is a happy news, being in SmalltalkHub completely disrupts the way we work here. Versionner does not run on Pharo 2.0, which means we cannot version Roassal (and the tools we planned to migrate to SHub) the way we have done up to now.
An easy fix to this is to use Pharo 1.4 to do the saving (I do not mind to do it until Versionner works on Pharo 2.0). How can Gofer be updated? In Pharo 2.0 Gofer supports some methods that do not exist in Pharo 1.4.
Another fix, is that we continue to work on squeaksource, and do some update time to time of SHub.
@Christophe: what is needed to have Versionner working on Pharo 2.0.
All our tools are properly versioned with a complete history. We cannot jeopardize this. This is not a good surprise.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Innovation comes in the least expected form. That is, if it is expected, it already happened."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev