On 18 May 2013 09:53, Frank Shearar <[email protected]> wrote: > On 18 May 2013 01:31, Camillo Bruni <[email protected]> wrote: >> Pharo 3.0 is now properly tracked on github >> >> - https://github.com/pharo-project/pharo-core > > Nice! How do you track the changes? From Jenkins as a build step?
What fileout format are you using? It looks like a custom job. (It's not chunk format or Filetree or gst style.) Although I'm not necessarily complaining here, since I have every intention of developing yet another fileout format. It turns out that Monticello can easily paper over the details of your fileout format - I have a (currently stalled because of unrelated issues) project that can load both fileout and Filetree formatted code from a GitHub repository, and from the perspective of the user, it's just Monticello. One request though - make a means of identifying the format please? At the moment FileTree puts a .filetree file in the repo, for instance. Perhaps if there are enough different filesystem formats we'll need to gather round and settle on a common identifier (.fileout-format, containing a symbol describing the format, or something), but at least today having a marker file means that a loader can easily figure out how to load the code. frank frank
