Hi Hannes,
This sounds right to me also. I just added a '5.2' SqueakMap release for FFI that hopefully does what you explain here.
If it looks right, we can "publish" it from the web page to make it official.
Thank you for making this happen for FFI :-)
Dave
On Sun, Oct 14, 2018 at 02:30:35AM +0200, H. Hirzel wrote:
Hello
Yes, in the meantime I have read through Chris Muller's email again and I understand that
a) the entry with the head script which contains
Installer new merge: #ffiTests' continues to be effective for future releases but will not help to document what works here and now in 5.2.
b) for 5.2 we need to create specific new release.
It should be labeled '5.2' because that follows the example set in
the current FFI entry. (**)
And assign it to Squeak release 5.2 so that it shows up in the
filtered list of 'newly safely-available package' for 5.2
Then entry may follow the example of Magma database (e.g. 1.62
server) which is
'SMSqueakMap default loadUpdates. (Smalltalk hasClassNamed: #MagmaSession)
ifFalse: [ SMSqueakMap default installPackageNamed: ''Magma'' version: ''1.62 client'' ].
#(''Magma-Server-cmm.515'' ''Magma-Tools-cmm.76'' ) do:
[ : each | (Installer repository: ''http://www.squeaksource.com/Magma'') install: each ]'
The issue is to go for specifc version of FFI code http://source.squeak.org/FFI/ The question now is which files to pick. I probably just pick the latest ones. The 'versions' page show a ConfigurationOfFFI-nice.41.mcz from Nicolas Cellier, April this year But I remember that Eliot Miranda has added better VM support
for exceptions regarding FFI, so I probably better go for his most recent
http://source.squeak.org/FFI/FFI-Kernel-eem.55.mcz and for the Pool dictionary values http://source.squeak.org/FFI/FFI-Pools-TorstenBergmann.4.mcz And for the tests FFI-Tests-cbc.9.mcz I'll do that on Monday unless somebody else wants to do it. The FFI package is 'community supported'. So anybody with which has a SqueakMap login may create it. Any comments?
--Hannes
** Other entries have different release numbering schemes, no need to label releases in synch with the Squeak releases.
On 10/14/18, Chris Muller ma.chris.m@gmail.com wrote:
It sounds like we need a new release called '5.2' with a load script that looks similar to the load script for '3.10' but with package versions that match what you get when you load '(head)'. That new release should be tagged for Squeak5.2, and it should be "published" from the http://map.squeak.org site. Does this sound right?
Yes, absolutely. And, once we have the template from this Squeak release established, it becomes incredibly easy to simply do what you said above, since you just select "Create New Release", and update version numbers in the script to what they show in the Monticello browser.
Any one of the 1.62 Magma packages can serve as the first template. Just delete the pre-req load if you don't need it and change the package names to the current correct versions of FFI.
- Chris