Hi Hannes,
I think you did not understand. Just because you "tested it and it worked" TODAY does not mean that script will continue working forever. That's why we MUST NOT put a "Squeak 5.2" tag on it unless we make a separate Release with a script that uses explicitly-specified versions.
That's what we have now, I see no versions of "FFI" for 4.5, only (head), 3.10, and 3.9. The last two were published by Andreas.
HTH, Chris On Fri, Oct 12, 2018 at 2:36 PM H. Hirzel hannes.hirzel@gmail.com wrote:
Hi Chris
I think that just
Installer new merge: #ffiTests
is good enough. Like it was for earlier version. I tested it and it worked.
I just wonder what I need to do that it shows up in the list of available packages for 5.2?
--Hannes
On 10/12/18, Chris Muller asqueaker@gmail.com wrote:
Hi Hannes,
It depends on what all we want do the work to catalog. "Installer new merge: #ffiTests" just loads the latest versions of all the packages, not a fixed configuration, so that script is not suitable to tag with any Squeak-specific versions, only the (head) version. If you want to make one for 5.2, we must use a totally different script which specifies the exact version #'s of all the packages, so we know it will always work in 5.2. You could copy & paste one of the scripts for one of my packages (Magma, etc.) which I just updated yesterday, BTW...
Best, Chris
The relevant FFI entry has as load script is just
Installer new merge: #ffiTests
This still applies for 5.2.
However the last time FFI shows up in the SqueakMap client list for a particular release is version 4.5.
Not in 4.6, 5.0 and 5.1
What do I need to do to make it appear in the list for 5.2.
Creating a release for 5.2 would be an option but that seems unnecessary as it had not been done for 4.5 either.
Suggestions how to proceed?
Regards Hannes