On 2013-05-18, at 10:53, Frank Shearar <frank.shearar@gmail.com> wrote:
On 18 May 2013 01:31, Camillo Bruni <camillobruni@gmail.com> wrote:
Pharo 3.0 is now properly tracked on github
Nice! How do you track the changes? From Jenkins as a build step?
Squeak doesn't do this yet, mainly because I've not got around to doing it. Because we don't use slices (maybe we should...) I'd pondered using a webhook off the squeaksource installation.
It uses the FileSystem-ST that maps packages/classes/methods to an internal FileSystem which can be easily written to disk: Gofer new smalltalkhubUser: 'dh83' project: 'FileSystemST'; package: 'ConfigurationOfFileSystemST'; load. (Smalltalk at: #ConfigurationOfFileSystemST) loadDevelopment. FileSystem st root copyAllTo: 'pharo-core' asFileReference.