Hi all, I've been playing around with Cog to see what it'd take to move the code to git. GitHub's svn importer [1] isn't very reliable I think (some directories were actually missing), but eventually I managed to convert the entire svn repo to git [2]. Also, I have been able to build different Cog VMs automatically on Travis CI. For a working build, see [3]. You can download the results at [4]. Please keep in mind that this is still a "test" ;) Eliot was also concerned how the version info will be maintained and I have a simple proposal: Each Cog release will be a git tag and for the version itself we could use semantic versioning [3]. Then the build version is the git tag, the date is the commit date and the URL is the "remote.origin.url". Here's an example: ==================================================================== 5.0-v0.1.0 Wed Mar 30 12:01:50 UTC 2016 gcc 4.6.3 [Production Spur 64-bit VM] CoInterpreter VMMaker.oscog-eem.1740 uuid: 10ece78d-d04d-4ad2-8598-e496b6a6097c Mar 30 2016 StackToRegisterMappingCogit VMMaker.oscog-eem.1740 uuid: 10ece78d-d04d-4ad2-8598-e496b6a6097c Mar 30 2016 VM: v0.1.0 https://github.com/fniephaus/squeak.git Date: Wed Mar 30 13:58:46 2016 +0200 Plugins: v0.1.0 https://github.com/fniephaus/squeak.git Linux testing-worker-linux-docker-9d959019-3394-linux-16 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux plugin path: ./products/nscogspur64linuxht/lib/nsvm/5.0-v0.1.0 [default: /home/idea4it/products/nscogspur64linuxht/lib/nsvm/5.0-v0.1.0/] ==================================================================== Any further suggestions? :) Best, Fabio |
yes, we are doing this since some time… one of the many advantages of being in git/github. (we also run pharo tests so we can "more or less” test the vm automatically.
+1 (but I think Eliot was concerned on the history already present in svn… for that, there are tools that migrate svn to git with all history, something like this: http://john.albin.net/git/convert-subversion-to-git)
“squeak” is a bad name :) “cog-vm”, “squeak-vm” (anything with “vm”, in fact) would be better :)
cheers! Esteban |
and I forget to mention that I’m highly excited with the idea of moving the development to git/github :) thank you very much for this, Fabio! Esteban
|
It's slowly happening, but I hope it /is/ happening ;) On Wed, Mar 30, 2016 at 3:25 PM Esteban Lorenzano <[hidden email]> wrote:
Eventually we might be able to do the same with Squeak, but first things first ;)
I will do another clean migration locally and a proper integrity check. I wouldn't want to use the GitHub importer
Sure thing, "squeak" was automatically created by the GitHub importer. Also, the repo won't be owned by my personal account ;) But that is the easy part :) |
Free forum by Nabble | Edit this page |