Hi, If anyone else is interested, you can load Xtreams using this expression: Gofer new squeaksource: 'Xtreams'; configuration; loadVersion: #bleedingEdge. I tested this only in Pharo 3.0, but it should work in 2.0 as well. Since all tests are green, it might be a good idea to set up a CI job. We could make a new stable config to put in the Configuration Browser repos. Sven
On Nov 20, 2013, at 5:17 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi,
If anyone else is interested, you can load Xtreams using this expression:
Gofer new squeaksource: 'Xtreams'; configuration; loadVersion: #bleedingEdge.
I tested this only in Pharo 3.0, but it should work in 2.0 as well.
cool!
Since all tests are green, it might be a good idea to set up a CI job.
We could make a new stable config to put in the Configuration Browser repos.
+1 Now what I really wonder is - what is the smallest core of Xtreams that we need to load code - could we have it a candleLight
Sven
On 20 Nov 2013, at 17:17, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi,
If anyone else is interested, you can load Xtreams using this expression:
Gofer new squeaksource: 'Xtreams'; configuration; loadVersion: #bleedingEdge.
I tested this only in Pharo 3.0, but it should work in 2.0 as well.
Since all tests are green, it might be a good idea to set up a CI job.
https://ci.inria.fr/pharo-contribution/job/Xtreams/ still a little rough, but it is a start.
We could make a new stable config to put in the Configuration Browser repos.
Sven
https://ci.inria.fr/pharo-contribution/job/Xtreams/
still a little rough, but it is a start.
If possible I would like to see the project itself moved over from SqS to STHub. Not as a "Pharo" fork but as a replacement for the Squeaksource repo. Sorry but I was too often bitten by SqS problems... Thx T.
On 21 November 2013 11:29, Torsten Bergmann <astares@gmx.de> wrote:
https://ci.inria.fr/pharo-contribution/job/Xtreams/
still a little rough, but it is a start.
If possible I would like to see the project itself moved over from SqS to STHub.
Not as a "Pharo" fork but as a replacement for the Squeaksource repo. Sorry but I was too often bitten by SqS problems...
Fair enough, and "once bitten twice shy", but please give SqS a chance: it's on a new box, running an updated image, and admins are actually watching out for the box. If you see any kinds of problems, I'm sure Chris Muller will want to hear about them. frank
Thx T.
On Thu, Nov 21, 2013 at 12:29:36PM +0100, Torsten Bergmann wrote:
https://ci.inria.fr/pharo-contribution/job/Xtreams/
still a little rough, but it is a start.
If possible I would like to see the project itself moved over from SqS to STHub.
Not as a "Pharo" fork but as a replacement for the Squeaksource repo. Sorry but I was too often bitten by SqS problems...
For information: The squeaksource.com service is now hosted on a different server, and is maintained by the Squeak community. The previous reliability and performance problems have been resolved. I don't want to discourage anyone from moving to other repositories, but you should not feel like you have to do it on account of the previous reliability issues. FYI only, Dave
participants (5)
-
David T. Lewis -
Frank Shearar -
Stéphane Ducasse -
Sven Van Caekenberghe -
Torsten Bergmann