Remove everything related to Pharo < 4 from baseline

[jecisc]

Because now Seaside is only for Pharo 4+

[jecisc]

We can also remove packages used only for Pharo < 5 and merge the packages like Javascript-Pharo20-Core with Javascript-Pharo-Core

[jecisc]

Hum... Not so easy. I have the impression that packages named "pharo" are loaded by squeak...

Maybe we should rename *-Pharo-* into *-Squeak-* and *-Pharo20-* into *-Pharo-*?

[jbrichau]

We are still testing for Pharo3 and 4 ... see travis line-up

[jecisc]

I do not see Pharo 3 and 4 in the travis.ymd file

[jecisc]

Oh, in the dev branch I see Pharo 4 but not 3.

[jbrichau]

Right. I meant 4 and 5.
We added 4 back because we could make the loading and testing work with metadataless filetree anyway.

I'm not sure renaming the Pharo20 package is a good idea when people would be upgrading their existing Seaside install in a Pharo 6 (or even 7). What happens when you first load master and then your branch?

[jecisc]

It will probably move all the methods to the new package and leave an empty Pharo20 package I guess.

[jecisc]

I find it a little confusing to have a package named "Pharo" that is only loaded in squeak and a package named "Pharo20" that is the default one for Pharo.

[jbrichau]

I agree and it would be great to have that fixed. I'll run over the changes and integrate it.

[jecisc]

My PR is only a first step. Since it impacts multiple smalltalk and a complex baseline I wanted to do it by steps.

[jecisc]

If you prefer a PR with all the changes at once to review tell me and I'll do the other changes.

[jbrichau]

Steps are good. Hold on a moment as I rename package extensions for Pharo7...

[marschall]

The only thing referencing the old versions is the gettext baseline, this is addressed by #1131 .

And Javascript has a different baseline for Pharo 7.x so I'm closing this.