Thanks Bert for the reply. <div class="gmail_quote">On Thu, Jun 7, 2012 at 8:27 PM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>> wrote: <blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 07.06.2012, at 15:57, Ajay Garg wrote: > Hi Bert. > > a) > Could you give a rough idea, as to what is the release cycle for squeak-vm? There is no fixed release cycle, releases are done as needed and as time permits. Once or twice a year has been typical. What is your time frame? If need be one could package a Squeak VM + patches. </blockquote><div> </div><div> Well, we need the squeak-vm (with the "Mpeg3Plugin.c" fix) for ceibal right-away. It will be best, if you could provide with any of the following options :: a) "squeak-vm-4.4.47 RPM for x86 "AND "squeak-vm-4.4.47 RPM for ARM". OR b) "squeak-vm-4.4.47 SRPM". </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> > b) > Also, I installed etoys-5.0.2406 rpm; and did (as told by you) "update code from server". > However, upon reboot, I again have to do "update code from server". No need to reboot, quitting Etoys is enough. Any changes made are not permanent, to encourage free experimentation without breaking anything. Normally Etoys only stores projects (which can contain code), the image is read-only. > So, is there a way that a "final" etoys image (incorporating all the latest changes) can be retrieved (locally)? That is, we may do all the updating from "update code from server", and then transfer the "final" etoys.image at will? Of course there is a way ;) First, copy some files from /usr/share/etoys over to Etoys' $SUGAR_ACTIVITY_ROOT/data direcory: [olpc@xo-a7-4a-a4 ~]$ cd .sugar/default/org.vpri.EtoysActivity/data [olpc@xo-a7-4a-a4 data]$ cp /usr/share/etoys/etoys.{image,changes} . [olpc@xo-a7-4a-a4 data]$ ln -s /usr/share/etoys/{locale,ExampleEtoys,EtoysV5.stc} . [olpc@xo-a7-4a-a4 data]$ ll insgesamt 17424 -rw-r--r-- 1 olpc olpc 5014 7. Jun 14:34 etoys.changes -rw-r--r-- 1 olpc olpc 17823140 7. Jun 14:34 etoys.image lrwxrwxrwx 1 olpc olpc 28 7. Jun 14:34 EtoysV5.stc -> /usr/share/etoys/EtoysV5.stc lrwxrwxrwx 1 olpc olpc 29 7. Jun 14:34 ExampleEtoys -> /usr/share/etoys/ExampleEtoys lrwxrwxrwx 1 olpc olpc 23 7. Jun 14:34 locale -> /usr/share/etoys/locale drwxrwxr-x 3 olpc olpc 4096 7. Jun 14:20 MyEtoys drwxrwx--- 3 olpc olpc 4096 31. Mai 17:53 private (you could also make the files in /usr/etoys/share writable, but copying is safer) (if your XO uses Rainbow security, the Etoys $SUGAR_ACTIVITY_ROOT will be somewhere in the isolation directory instead) The next time you launch Etoys, it will use this image at $SUGAR_ACTIVITY_ROOT/data/etoys.image instead. (Etoys also looks for a developer image on a USB stick, see Etoys.activity/bin/etoys-activity and use whatever is most convenient) Now you are ready for serious Squeak development. 1) The secret is Alt-Shift-W. Press this to bring up the full Squeak world menu. 2) From the menu, choose "previous project". This will jump to a hidden unnamed project. You should recolor this project to remind you this is not the default Etoys anymore (right-click, use the lower-right halo handle to choose a different background color) 3) Load updates 4) Press Alt-Shift-W again, choose "save and quit". Do not use "save as" or "save new version" because those would create new file names. Done. The next time you launch Etoys, you will see it using your image (because of the different background color). Always go back to the top-level project before saving. Of course, this will also retain all changes you make, windows you have open etc. Make yourself a nice dev environment :) (there is an older version of these instructions, plus a nice tutorial, at <a href="http://wiki.laptop.org/go/Smalltalk_Development_on_XO" target="_blank">http://wiki.laptop.org/go/Smalltalk_Development_on_XO</a> ) </blockquote> <div> Thanks a ton !!!! So, all we need to do is replace the "old" etoys.image and etoys.changes with the "latest" etoys.image and etoys.changes, respectively? If yes, then we would be needing the SRPM for etoys-5.0.2406. (Or the older SRPM for etoys-4.1 would do ?) Thanks and Regards, Ajay </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> - Bert - _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div>