what is cruelly needed is a build integration server. Keith is working on Bob and he needs help. Now what is needed is that people go also over the code of keith to minimize overrides and other things, else we will have again such discussion and people will get frustrated and think we are assholes (which is not the case) :). In pharo we really want to avoid overrides and extensions for the sake of them. So this means that we should integrate changes. I'm planning to go over kernel extensions today. following the mail and analysis we did with damien in october (argh) Stef On Feb 14, 2009, at 1:17 AM, Geert wrote:
Keith Hodges wrote:
Squeaksource is the place to manage the source that makes up a project. You can also set up your own repositories (with ftp for example), much like other scm tools.
SqueakMap/Universes/ and Sake/Packages are places to publish the end results of projects, for others to load.
SqueakMap - is intended to be the directory of all packages, but it doesn't support dependencies.
Universes - has packages with dependencies targeted for a specific version of squeak.
Sake/Packages - has package definitions browseable in a standard class browser - supports dependencies - supports unloading - load current published / or latest beta code it can find
hope this helps clarify our murky world
Keith
Thanks Keith, I had not heard of Sake before ... other than it being a beautiful Japanese beverage :)
All these things do seem to serve a different purpose. Would it be an idea to simplify things a bit to make it easier to collaborate, share and innovate? -- View this message in context: http://n2.nabble.com/Distributed-versioning-...-MonticelloHub--tp2319149p232... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project