On 03/27/14 10:46, Fred wrote: > On 03/26/14 22:44, Stuart Cassoff wrote: >> This update of Scratch needs the new Squeak. >> Port tarball supplied though diff not that bad. >> >> No need to build any plugins; all needed plugins available via the vm port. >> Adding a dependency on Squeak sources v2 and installing changes file >> allows users to modify Scratch. >> Removed homegrown startup script. >> The supplied startup script is now installed. May need modification. >> Ports var adjustments for better(?) PLIST. >> >> There are some hard-coded directories (like /usr/share) in >> the Scratch image and aiui changes cannot be automated. >> If adjusted then all available languages would appear in the language menu >> and the "Examples" button in the file dialog would go to the installed >> examples. >> Other problems, if any, can be fixed as well. >> Some person would have to make the changes manually and then repackage the >> distfile. >> >> >> Stu >> > > Hi Stu, > > Lightly tested on amd64 - using the new squeakvm that you posted. > Will try to test i386 and macppc in the next week (I'm away this weekend). > > When starting scratch I have to do: > > SC_DIR=/usr/local/share/scratch/ scratch > > other wise it says: > > port:fred /var/www> scratch > Executing: /usr/local/lib/squeak/squeakvm/squeakvm /Scratch.image > Could not open the Squeak image file `/Scratch.image'. > > There are three ways to open a Squeak image file. You can: > 1. Put copies of the default image and changes files in this directory. > 2. Put the name of the image file on the command line when you > run squeak (use the `-help' option for more information). > 3. Set the environment variable SQUEAK_IMAGE to the name of the image > that you want to use by default. > > For more information, type: `man squeak' (without the quote characters). > > Thanks for the update, cheers > > Fred > >
Great, thanks! Hm, the startup script needs adjusting. You can skip it and run the vm directly. Stu
