Updated squeak-vm-3.4.5170.ebuild for inclusion into Portage tree. lintool reports 0 errors, 0 warnings. This version of the ebuild will run with ANY squeak version, choosing the latest version in Portage as the default to install if no version has been previously installed. Squeak operates on the principle of a virtual machine and an image file. In portage, the virtual machine is the dev-lang/squeak package, and the image file is the dev-lang/squeak-vm package. A little convoluted, but hey ... This ebuild will install the Squeak 3.4-5170 image file; it RDEPENDS on ANY squeak image to be installed (dev-lang/squeak), and will install the latest version in Portage if that dependency fails. This makes this version of the ebuild backwards compatible with Squeak 3.2.* virtual machines. Reproducible: Always Steps to Reproduce:
Created attachment 12229 [details] Changelog for the ebuild
Created attachment 12230 [details] Actual ebuild
As i already checked in your squeak-vm-3.5.5180.ebuild is it neccessary to include this ebuild into portage or should i close the bug?
*** Bug 16814 has been marked as a duplicate of this bug. ***
Because different Squeak programmers may want to run different image versions (e.g. a 3.4-5170 image for one person, a 3.5-5180 image for another) like the class I'm a teaching assistant for does, having the 3.2, 3.4, and 3.5 image in Portage would be useful.
Ok, so i'll check this ebuild in, too. Closing this bug and thanks for your quick response.
