I did not load updates - that might be the difference. But there is also a difference in the vm. The web site says to "just use the vm from 1.3" which I took to be the one-click? So I renamed and copied the 1.4 image and changes into the resources directory. It make one think there should be a better way, maybe there is? For this image, I simply dumped 1.4 and Cog-linux from Jenkins into one folder and made a shell script to run the image. Overall, that is a much simpler process. If it is sound, it might be best to reduce the number of links on the site and to recommend the above for using 1.4. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker@inria.fr] Sent: Thursday, February 09, 2012 3:32 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins On Feb 9, 2012, at 9:23 PM, Schwab,Wilhelm K wrote:
Miguel,
Giving you the benefit of the doubt, you misunderstand. Something did change "suddenly" in my experience and (as I ****CLEARLY**** stated in my email), it could easily be that the links on the Pharo site are stale.
They are not. At least a) the link to 1.4 points to update 315, which is just 9 updates old. And for sure you would do a "load updates" anyway? The download is just a copy from the build server. (same .zip, renamed), of some days ago. This is used by jenkins. Jenkins does nothing else then "load updates" and save. Marcus -- Marcus Denker -- http://marcusdenker.de