upgrade ECL to 15.3.7

[dimpase]

ECL we ship is very old. Here is an update to the current stable version.

• ECL git ​here and the tarball can be obtained ​there, too. But it is not useful without renaming, patching, and running autoconf. This from it we create an updated tarball by running spkg-src script.

ECL tarball to use is ​here

[fbissey]

I thought you were going to update spkg-src to run autotools, have I been mistaken on that point? Other than that I cannot really check the patch for cygwin but I am assuming they would be OK. The other stuff done to the tarball and then as a consequence to the configure script are a bit extreme in my view but I can keep to the status quo.

[dimpase]

Replying to fbissey:

I thought you were going to update spkg-src to run autotools, have I been mistaken on that point?

Right, thanks for reminding me. I'll update spkg-src.

[dimpase]

Replying to dimpase:

Replying to fbissey:

I thought you were going to update spkg-src to run autotools, have I been mistaken on that point?

Right, thanks for reminding me. I'll update spkg-src.

But running autoconf in spkg-src would only make sense if almost all patches are applied already. So in effect we are creating a modified tarball, if we are not willing to have autoconf as a dependence.

I don't know, tell me if this is OK, or not...

PS. On the other hand I can just do patching in spkg-src and again in spkg-install.

[fbissey]

sage-src point is that we ship a modified tarball and it helps generate it. In my opinion running autoreconf is fair game. You have to remember spkg-src is not run by the user building sage only by the packager providing a new version of the package.

That being said the change allowed in are only things that are not trivial:

• removal of files (making a smaller tarball, gap anyone?)
• regeneration of script (autoreconf is a case in point if the changes are not easily patched back into configure and al. It is generally cleaner.)

Whether you want to exercise the second bullet point is at your discretion. I didn't for the last singular patch, but it was a trivial change.

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​06082f6

moved patching into spkg-install, and other updates around this

[dimpase]

OK, done; I have moved all the patching into spkg-src, and further updated it to make creation of the tarball etc as automatic as I can. As a byproduct, spkg-install is simpler.

[dimpase]

oops, wrong tarball naming...

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​c4db169

updated...

[fbissey]

Sorry to be a pain but I would like you to add a comment in SPKG.txt that from this release all the patches are applied in spkg-src and therefore do not need to be applied in spkg-install. I would go as far as adding a comment in spkg-install signalling that patches are already applied from spkg-src. I believe that's the first package to take a total inclusion course from spkg-src in this way.

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​6bb249b

updated SPKG.txt, added message to spkg-install, fixed patching

[dimpase]

New commits:

​c4db169	updated...
​6bb249b	updated SPKG.txt, added message to spkg-install, fixed patching