Howdy -
Congratulations everybody on the Pharo 6.0 release! I want to package this up for NixOS Linux now. Can somebody please tell me how to choose the right Git commit for the current stable Pharo 6.0 VM for Linux? Currently I am using commit 1c38b03fb043a2962f30f080db5b1292b5b7badb but I assume that a newer version is expected now & that more updates will follow in the future. Cheers! -Luke |
Hi Luke,
On 29 June 2017 at 18:23, Luke Gorrie <[hidden email]> wrote: > Howdy - > > Congratulations everybody on the Pharo 6.0 release! > > I want to package this up for NixOS Linux now. Can somebody please tell me > how to choose the right Git commit for the current stable Pharo 6.0 VM for > Linux? > > Currently I am using commit 1c38b03fb043a2962f30f080db5b1292b5b7badb but I > assume that a newer version is expected now & that more updates will follow > in the future. git clone https://github.com/OpenSmalltalk/opensmalltalk-vm.git cd opensmalltalk-vm git checkout 6a63f68 Esteban has done some work on Iceberg and the 64 bit VM, so I'd expect a new one soon. Cheers, Alistair |
Thanks Alistair! How did you choose that specific commit? (How can I tell what is current next month, and the month after, etc?) On 29 June 2017 at 18:29, Alistair Grant <[hidden email]> wrote: Hi Luke, |
On Thu, Jun 29, 2017 at 07:50:11PM +0200, Luke Gorrie wrote:
> Thanks Alistair! > > How did you choose that specific commit? (How can I tell what is current next > month, and the month after, etc?) I periodically download the current VM and check the version: $ curl get.pharo.org | bash $ ./pharo --version 5.0-201705310241 Wed May 31 04:57:44 UTC 2017 gcc 4.6.3 [Production Spur ITHB VM] CoInterpreter VMMaker.oscog-eem.2231 uuid: de62947a-7f40-4977-a232-e06a3a80c939 May 31 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2227 uuid: 7ea146b4-39ce-4de7-afa3-a76ed1d1da35 May 31 2017 VM: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 30 19:41:27 2017 -0700 $ Plugins: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Linux testing-gce-3510e247-0aff-4711-8b5e-035fd311d6b8 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 i686 i686 i386 GNU/Linux plugin path: /tmp/p6/pharo-vm/lib/pharo/5.0-201705310241 [default: /tmp/p6/pharo-vm/lib/pharo/5.0-201705310241/] Looking through the text above you can see which repository was used for the build: VM: 201705310241 https://github.com/OpenSmalltalk/opensmalltalk-vm.git and the timestamp from the commit: $ Date: Tue May 30 19:41:27 2017 -0700 $ Clone the repository, check out the Cog branch, and search through the log for the appropriate commit timestamp: commit 6a63f68a3dd4deb7c17dd2c7ac6e4dd4b0b6d937 Author: Eliot Miranda <[hidden email]> Date: Tue May 30 19:41:27 2017 -0700 HTH, Alistair > On 29 June 2017 at 18:29, Alistair Grant <[hidden email]> wrote: > > Hi Luke, > > On 29 June 2017 at 18:23, Luke Gorrie <[hidden email]> wrote: > > Howdy - > > > > Congratulations everybody on the Pharo 6.0 release! > > > > I want to package this up for NixOS Linux now. Can somebody please tell > me > > how to choose the right Git commit for the current stable Pharo 6.0 VM > for > > Linux? > > > > Currently I am using commit 1c38b03fb043a2962f30f080db5b1292b5b7badb but > I > > assume that a newer version is expected now & that more updates will > follow > > in the future. > > git clone https://github.com/OpenSmalltalk/opensmalltalk-vm.git > cd opensmalltalk-vm > git checkout 6a63f68 > > Esteban has done some work on Iceberg and the 64 bit VM, so I'd expect > a new one soon. > > Cheers, > Alistair |
In reply to this post by alistairgrant
On 29 June 2017 at 18:29, Alistair Grant <[hidden email]> wrote: git clone https://github.com/ Just in quick happy testing... The 32-bit VM seems to be fine the 64-bit VM is not working properly since I updated to this commit. I open Pharo64-60465.image and initially it looks okay - Pharo logo and dark theme - but when I try to open windows - world menu, playground, spotter - the graphics are garbled for the screen areas that should be updated. I am tempted to ignore this problem for now because I don't know how stable the 64-bit VM is supposed to be, how backwards compatible it is supposed to be with slightly older images, what test suite I should run to check its basic functions, etc. Tips welcome! I will gladly improve this in the future. Cheers, -Luke |
Free forum by Nabble | Edit this page |