Will Gutsy be release with a fixed version of Squeak?
To be honest this situation is a blocker and should be relabelled as such.
A person installs the Squeak packages, tries to run squeak, is told in the manual to run inisqueak only to find that it doesn't exist. I suspect most people will then remove the Squeak packages and go and use Ruby.
The startsqueak script does not do the right thing in that it copies files to the central location ~/squeak. The whole point of the inisqueak way of doing things is that you can have any number of active images. Create a directory, create an image, go.
Does startsqueak have any documentation? man startsqueak says no documentation and startsqueak --help just copies an image and starts just as though no option was given.
I am happy that there is a Gnome menu entry etc. for those people who use such things, but surely just having the inisqueak command as is documented is easy to do, and satisfies all the people who use Squeak the way it is intended to be used.
Will Gutsy be release with a fixed version of Squeak?
To be honest this situation is a blocker and should be relabelled as such.
A person installs the Squeak packages, tries to run squeak, is told in the manual to run inisqueak only to find that it doesn't exist. I suspect most people will then remove the Squeak packages and go and use Ruby.
The startsqueak script does not do the right thing in that it copies files to the central location ~/squeak. The whole point of the inisqueak way of doing things is that you can have any number of active images. Create a directory, create an image, go.
Does startsqueak have any documentation? man startsqueak says no documentation and startsqueak --help just copies an image and starts just as though no option was given.
I am happy that there is a Gnome menu entry etc. for those people who use such things, but surely just having the inisqueak command as is documented is easy to do, and satisfies all the people who use Squeak the way it is intended to be used.