Hey, I wrapped the Squeak VM and Squeak 3.2-4956 image into two separate ebuilds. Squeak is a unique language in that it comes as four parts: (1) Virtual Machine (2) Sources File (3) Changes File (4) Image File The Virtual Machine will load the Sources file to get the "base" of the language, and then it will load the Image file (and subsequently the Changes file) to get any user-modifications. Squeak.org, the maintainer of Squeak, will updated the VM And the Sources/Changes/Image independently of each other, so I propose two categories under dev-lang: (1) dev-lang/squeak-vm (2) dev-lang/squeak-img You can run multiple image and virtual machine versions (such as VM 3.2-5 and Image 3.2-xxxx, as well as VM 3.1-6 and Image 3.4-xxxx), so keeping these trees separate will allow for the highest level of customization for the user. All image ebuilds should be dependent upon dev-lang/squeak-vm being installed though. :-) (Not vice versa...) All dependencies already exist inside the ebuild system. The interdependency of squeak-img with squeak-vm is handled by submitting both of these at the same time. chris verges squirrel@mail.headnut.org
Created attachment 5733 [details] Squeak Virtual Machine 3.2-5
Created attachment 5734 [details] Squeak image/changes 3.2-4956 and V3sources
I tested the vm ebuild, and it installs its files in non-compliant places [excerpt]: >>> /doc/squeak/ >>> /lib/squeak/ --- /usr/local/ >>> //bin/squeak -> ..//usr/local/lib/squeak/3.2-5/squeak 1) /doc/squeak should go into /usr/share/doc/${P} 2) /lib/squeak should go into /usr/lib/squeak 3) /usr/local/ <- this is COMPLETELY off limits to the distros packages, that space is exclusively administered by the sysadm. Place stuff in /usr/ instead. 4) /bin/squeak should of course be in /usr/bin/squeak Would you mind resubmitting an ebuild where these path problems have been fixed ?
Didn't hear any more on this; marking it as invalid.
