On Sat, Apr 15, 2017 at 02:14:26PM +0200, Luke Gorrie wrote: > On 15 April 2017 at 11:53, Alistair Grant <akgrant0...@gmail.com> wrote: > > (actually, I'm not sure why you're bothering since 6 should > be out before the end of the month, but that's your choice :-)). > > > I just want something stable and reasonably modern for running existing > applications and building new ones. > > If that means waiting for Pharo 6.0 release then that is okay with me. > > > The (V6) linux install relies on a number of bash scripts to launch pharo > (bin/pharo, bin/pharo-ui and bin/pharo-vm/pharo). How are you producing > these, or are you doing something else? > > > Here is where those scripts are generated in the existing pharo-vm packaging: > https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/pharo/vm/ > build-vm.nix#L50-L70
Ahh, so Nix is doing its own thing, not using the ZeroConf scripts. > (I didn't write the nix packaging code but I have volunteered to maintain it > so > if it's out of date then I should fix that.) It will be for V6. Esteban has changed the scripts to ensure that Pharo versions of libraries are loaded (from memory)(this is also partly why I would like to use the full build process). > git clone https://github.com/pharo-project/pharo-vm.git > git checkout <the stable code...> > cd pharo-vm/opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build > ./mvm > -- > > BTW: HEAD is currently eaf13db484ac87720d8454e66b5ce92f51c01036, and my > experience is that it is significantly less stable than the latest > binary, which is from 1c38b03fb043a2962f30f080db5b1292b5b7badb > > > This is really the bleeding edge :-) both of those commits were pushed within > the past three days! Yep, V6 is still in testing. :-) Cheers, Alistair
