On Fri, Oct 12, 2018 at 10:05:40PM +0200, H. Hirzel wrote:
> Hi Chris
>
> On 10/12/18, Chris Muller <
[hidden email]> wrote:
> > 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.
>
> There is no such claim. The claim is just that it still works for 5.2.
+1
>
> > 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.
>
> And that contains
>
> Installer new merge: #ffiTests'
>
> That means this script has been working since 3.9, i.e. for 10 years.
+1
Chris, this is important. We have to have some way to handle the
use case that Hannes is trying to handle here.
As a package maintainer, I do /not/ want to declare a new release
of my package unless unless I have actually released something new
in my package, because that forces me to declare a new release of
my package when no such thing has actually happened.
When someone in the Squeak or Cuis or Pharo community decides to
announce a new release of their image distribution, I /do/ want
to announce my claim that some version of my package works with
that release, because I want to let that community know that my
package still works with their new release.
We need some way to deal with this use case. "Make another bogus
release of your package every time somebody in Sqeak/Cuis/Pharo
decides to announce a new release of their image" is not really
a very good answer. it kind of works but ... yuk.
Dave
>
>
> --Hannes
>
> > HTH,
> > Chris
> > On Fri, Oct 12, 2018 at 2:36 PM H. Hirzel <
[hidden email]> 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 <
[hidden email]> 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
> >> >>
> >> >
> >> >
> >
>
Locked
