Official packages on pharo.com - broken

Hello,

look at this page:
http://pharo.org/gnu-linux-installation

and try to download "libc < 2.15" or "centos" versions.
Both are broken - error message immediately after start:

"This interpreter (vers. 6505) cannot read image file (vers. 6521)."

So, the first impression is really terrible (don't work at all).
Default GNU/Linux download is probably OK.

pf

Od: Peter Uhnák Odesláno: pátek, 17. června 2016 14:46 Komu: Pharo Development List Odpovědět: Pharo Development List Předmět: Re: [Pharo-dev] Official packages on pharo.com - broken

> On 17 Jun 2016, at 15:15, Petr Fischer <[hidden email]> wrote:
>
> It's due to my obscure OS (‎FreeBSD, latest). They have Linux compatibility (even 64bits soon), so it's nice, but libs are from CentOS6 (now) with glibc 2.12 etc etc.
>
> But disfunct downloads on pharo.org is bad. ‎Removing obsolete thinks from official website is not bad idea.

It is not dysfunctional, it is legacy, that is important too.
If you want us to drop our own older releases, than we should also drop old/weird linux versions ;-)
But of course, it should be better described to avoid the confusion.

On Fri, Jun 17, 2016 at 03:24:37PM +0200, Sven Van Caekenberghe wrote:
>
> > On 17 Jun 2016, at 15:15, Petr Fischer <[hidden email]> wrote:
> >
> > It's due to my obscure OS (‎FreeBSD, latest). They have Linux compatibility (even 64bits soon), so it's nice, but libs are from CentOS6 (now) with glibc 2.12 etc etc.
> >
> > But disfunct downloads on pharo.org is bad. ‎Removing obsolete thinks from official website is not bad idea.
>
> It is not dysfunctional, it is legacy, that is important too.

It is dysfunctional in the sense that it claims it's for Pharo 5, which is no longer true since December (or whenever we've switched to Spur).

The action should be either:

a) remove the link altogher
b) say that it's only for Pharo 4 (if you want to support legacy)

In addition to that, if you want backward compatiblity (legacy argument here imho fails, because Pharo 5 has been released a month ago)

1) build spur with glibc <2.15 and add it as a download for Pharo 5

I think there's no point in doing this as you are just increasing maintenance/legacy burden down the road, but I wouldn't be the one doing that so that's not my call.

Peter

On Fri, Jun 17, 2016 at 2:56 PM, Peter Uhnak <[hidden email]> wrote:

On Fri, Jun 17, 2016 at 03:24:37PM +0200, Sven Van Caekenberghe wrote:

> On 17 Jun 2016, at 15:15, Petr Fischer <[hidden email]> wrote: > > It's due to my obscure OS (‎FreeBSD, latest). They have Linux compatibility (even 64bits soon), so it's nice, but libs are from CentOS6 (now) with glibc 2.12 etc etc. > > But disfunct downloads on pharo.org is bad. ‎Removing obsolete thinks from official website is not bad idea. It is not dysfunctional, it is legacy, that is important too.

It is dysfunctional in the sense that it claims it's for Pharo 5, which is no longer true since December (or whenever we've switched to Spur). The action should be either: a) remove the link altogher b) say that it's only for Pharo 4 (if you want to support legacy) In addition to that, if you want backward compatiblity (legacy argument here imho fails, because Pharo 5 has been released a month ago) 1) build spur with glibc <2.15 and add it as a download for Pharo 5

I think there's no point in doing this as you are just increasing maintenance/legacy burden down the road, but I wouldn't be the one doing that so that's not my call. Peter