Hi Alistair, > On Jun 29, 2017, at 1:23 PM, Alistair Grant <[hidden email]> wrote: > >> 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 Feel free to add a script to the scripts directory that automates this. e.g. scripts/checkoutVMbyDate ? > > > 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 > |
Hi Eliot, On Thu, Jun 29, 2017 at 01:29:30PM -0700, Eliot Miranda wrote: > > Hi Alistair, > > > On Jun 29, 2017, at 1:23 PM, Alistair Grant <[hidden email]> wrote: > > > >> 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 > > Feel free to add a script to the scripts directory that automates > this. e.g. scripts/checkoutVMbyDate ? Good idea, I'll put together a pull request. Cheers, Alistair |
Hi Eliot & Luke, On Fri, Jun 30, 2017 at 07:44:01AM +0000, Alistair Grant wrote: > > ... > > > Feel free to add a script to the scripts directory that automates > > this. e.g. scripts/checkoutVMbyDate ? > > Good idea, I'll put together a pull request. > > Cheers, > Alistair OK, I enjoy writing bash scripts almost as much as writing perl, and I refuse to write perl, so... I'm open to suggestions for improving the script, coding styles, etc. The script can be found at: https://github.com/akgrant43/opensmalltalk-vm/blob/checkoutVMbyDate/scripts/checkoutVMbyDate It's a single file, so should be easy to copy and test. If you're happy with what's there, let me know and I'll create a PR. The help text is: checkoutVMbyDate [-dewh] -- Checkout the commit with the matching timestamp -d = Display the hash only, don't check out. -h = Display this help text and exit. Three forms are supported: 1. By date: checkoutVMbyDate DATE E.g.: checkoutVMbyDate "Tue May 30 19:41:27 2017 -0700" Note that this is doing a simple string match, so the date must be in the same format as git log. 2. By executable: checkoutVMbyDate -e PHARO_EXE E.g.: checkoutVMbyDate -e /path/to/pharo Run the supplied executable with the --version option and look for the date string. 3. By URL checkoutVMbyDate -w PHARO_URL E.g.: checkoutVMbyDate -w get.pharo.org This will execute "curl PHARO_URL | bash" in /tmp/checkoutVMbyDate/, run the downloaded exe and find the date string. -- Cheers, Alistair |
Hi Alistair, looks good to me. Put in a PR. We can refine the script if necessary when it's in use. _,,,^..^,,,_ (phone) > On Jul 2, 2017, at 8:42 AM, Alistair Grant <[hidden email]> wrote: > > > Hi Eliot & Luke, > > On Fri, Jun 30, 2017 at 07:44:01AM +0000, Alistair Grant wrote: >>> ... >> >>> Feel free to add a script to the scripts directory that automates >>> this. e.g. scripts/checkoutVMbyDate ? >> >> Good idea, I'll put together a pull request. >> >> Cheers, >> Alistair > > > OK, I enjoy writing bash scripts almost as much as writing perl, and I > refuse to write perl, so... I'm open to suggestions for improving the > script, coding styles, etc. > > The script can be found at: > https://github.com/akgrant43/opensmalltalk-vm/blob/checkoutVMbyDate/scripts/checkoutVMbyDate > > It's a single file, so should be easy to copy and test. > > If you're happy with what's there, let me know and I'll create a PR. > > The help text is: > > checkoutVMbyDate [-dewh] -- Checkout the commit with the matching timestamp > > -d = Display the hash only, don't check out. > -h = Display this help text and exit. > > Three forms are supported: > > 1. By date: > > checkoutVMbyDate DATE > > E.g.: > > checkoutVMbyDate "Tue May 30 19:41:27 2017 -0700" > > Note that this is doing a simple string match, so the date must be in the same > format as git log. > > > 2. By executable: > > checkoutVMbyDate -e PHARO_EXE > > E.g.: > > checkoutVMbyDate -e /path/to/pharo > > Run the supplied executable with the --version option and look for the date > string. > > > 3. By URL > > checkoutVMbyDate -w PHARO_URL > > E.g.: > > checkoutVMbyDate -w get.pharo.org > > This will execute "curl PHARO_URL | bash" in /tmp/checkoutVMbyDate/, run the > downloaded exe and find the date string. > > -- > > Cheers, > Alistair |
On Sun, Jul 02, 2017 at 08:19:27PM -0700, Eliot Miranda wrote: > > Hi Alistair, > > looks good to me. Put in a PR. We can refine the script if necessary when it's in use. Done: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/143 Cheers, Alistair |
Free forum by Nabble | Edit this page |