Update to FriCAS 1.2.4

[hemmecke]

The earlier upgrade is in #9354. See also #6517 for more information.

Source tarball:

http://sourceforge.net/projects/fricas/files/fricas/1.2.4/fricas-1.2.4-full.tar.bz2/download

that has to be renamed into fricas-1.2.4.tar.bz2 (and put in $SAGE_ROOT/upstream) as usual.

Older instructions:

http://sage.math.washington.edu/home/hemmecke/pub/fricas-1.1.0.spkg

http://sage.math.washington.edu/home/hemmecke/pub/fricasaldor-1.1.0.spkg

fricasaldor might not properly work on 64 bit machines or might not work at all.

Link to project: http://sourceforge.net/projects/fricas/

CC: @hemmecke @rwst

Component: packages: experimental

Keywords: fricas

Author: Vincent Delecroix

Branch: 6ff2fdf

Reviewer: Frédéric Chapoton, Ralf Stephan

Issue created by migration from https://trac.sagemath.org/ticket/9465

[dimpase]

comment:3

Would you like to make an spkg with current Fricas?
I'll make sure to review it, etc.
Thanks!

[dimpase]

comment:4

for the record, fricas-1.0.9 spkg fails to install in Sage 4.8 on x86_64 Linux (Debian).

[hemmecke]

comment:5

Why are you considering 1.0.9? Above you find a link to 1.1.0. and
FriCAS progressed to 1.1.5.

However, in 1.1.5 the aldor-interface is broken. It's already fixed in trunk,
but I tend to wait till 1.1.6 is released in order to produce a new spkg.

Furthermore, quickly browsing over my spkg generation scripts, tells me,
that I will have to fix some small issues.

BTW, is it still required that FriCAS for Sage must use ECL and not SBCL?

Ralf

[dimpase]

comment:6

Replying to @hemmecke:

Why are you considering 1.0.9? Above you find a link to 1.1.0. and
FriCAS progressed to 1.1.5.

I was just pointing out that an upgrade is needed badly.

However, in 1.1.5 the aldor-interface is broken. It's already fixed in trunk,
but I tend to wait till 1.1.6 is released in order to produce a new spkg.

Furthermore, quickly browsing over my spkg generation scripts, tells me,
that I will have to fix some small issues.

BTW, is it still required that FriCAS for Sage must use ECL and not SBCL?

Was it ever required? I guess it was never assumed that SBCL is installed on the system, so by default
FriCAS can fall back on ECL provided by Sage.
(This would need a trivial adjustment of the spkg-install, I suppose).

On the other hand a fast interface to FriCAS would need an embeddable Lisp, and ECL fits this bill.

Dima

Ralf

[fchapoton]

Changed keywords from none to fricas

[videlec]

comment:15

Hi,

Could we ship the last version ?

November 24, 2014 -- FriCAS 1.2.4 released.

Vincent

[videlec]

comment:16

I wrote the spkg-install and it at least compile on my computer... If anybody want to test it

• download the source tarball fricas-1.2.4-full.tar.bz2, move it to $SAGE_ROOT/upstream and rename it fricas-1.2.4.tar.bz2
• switch to the git branch provided here
• run sage -i fricas and then make (from $SAGE_ROOT)

I am currently trying to see whether the interface is not broken...

Vincent

[videlec]

Branch: u/vdelecroix/9465

[videlec]

Changed author from Ralf Hemmecke to Vincent Delecroix

[sagetrac-git]

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

fd76b65

trac #9465: fricas package update

[sagetrac-git]

Commit: fd76b65

[videlec]

comment:19

Looks like it work -> needs review.

[fchapoton]

comment:21

I have added a few '#optional - fricas' so that the tests pass both with '-optional=fricas' and without, in 'interfaces/fricas.py'

---

New commits:

6ff2fdf

trac #9465 more # optional - fricas so that tests pass

[fchapoton]

Changed branch from u/vdelecroix/9465 to public/ticket/9465

[fchapoton]

Changed commit from fd76b65 to 6ff2fdf

[fchapoton]

comment:22

Looks good to me. If somebody else can confirm, this seems to be good to go.

[rwst]

comment:23

Wow, fricas has Puiseux series. Builds fine. Passes all tests in interfaces, rings, and structure.

[rwst]

Reviewer: Frédéric Chapoton, Ralf Stephan

[hemmecke]

comment:24

1. See also http://fricas.github.io

2. What exactly is the problem with fricas-aldor on 64bit machines?

3. Meanwhile Aldor is under the Apache License 2.0. So fricas-aldor could even install Aldor. Or there should be another spkg that installs Aldor and fricas-aldor might trigger installation of Aldor, if it is not already there.

[videlec]

comment:25

Replying to @hemmecke:

1. See also http://fricas.github.io

The documentation is much nicer there... why the project is both on sourceforge and github ?

2. What exactly is the problem with fricas-aldor on 64bit machines?

No idea... I have to try, where the source code is available ?

3. Meanwhile Aldor is under the Apache License 2.0. So fricas-aldor could even install Aldor. Or there should be another spkg that installs Aldor and fricas-aldor might trigger installation of Aldor, if it is not already there.

I guess it is safer to have separated packages. This ticket will be closed and contain only the fricas update. But we might open others for aldor/fricas-aldor.

Vincent

[hemmecke]

comment:26

Replying to @videlec:

The documentation is much nicer there... why the project is both on sourceforge and github ?

The project is officially on sourceforge and still under SVN. :-( But since I think git is tremendously better, I created a life mirror at github.
See https://sites.google.com/site/hemmecke/fricas-svn#fricas-devel for details.
I'd be happy if FriCAS switched completely to git, but that's not a big issue with mainly only Waldek and me commiting to the code base.

2. What exactly is the problem with fricas-aldor on 64bit machines?

No idea... I have to try, where the source code is available ?

Source code of what?

Aldor: https://github.com/pippijn/aldor
fricas-aldor spkg: ummmm.... I used to have a hg repo somewhere on my sagemath account, but don't know what the computer is that I have to login. I would then try to convert it to git and put it to github.

I guess it is safer to have separated packages. This ticket will be closed and contain only the fricas update. But we might open others for aldor/fricas-aldor.

Please do that and put me into the CC. I'm currently a little unfamiliar with Sage development.

[videlec]

comment:27

Replying to @hemmecke:

Replying to @videlec:

2. What exactly is the problem with fricas-aldor on 64bit machines?

No idea... I have to try, where the source code is available ?

Source code of what?

Aldor: https://github.com/pippijn/aldor
fricas-aldor spkg: ummmm.... I used to have a hg repo somewhere on my sagemath account, but don't know what the computer is that I have to login. I would then try to convert it to git and put it to github.

It would be better to have a link to a stable release with a version number (i.e. "an official tarball"). Otherwise we need to artificially create one.

I guess it is safer to have separated packages. This ticket will be closed and contain only the fricas update. But we might open others for aldor/fricas-aldor.

Please do that and put me into the CC. I'm currently a little unfamiliar with Sage development.

To create packages the documentation is very well written: http://sagemath.org/doc/developer/packaging.html (I might help for that step). Then there is the second step of having an interface within sage (I have very little experience with that).

Vincent

[fchapoton]

comment:28

See #9427 for a follow-up ticket on integration.

[vbraun]

comment:29

No $@#$ sourceforge links the next time, please.

[vbraun]

Changed branch from public/ticket/9465 to 6ff2fdf

[jdemeyer]

comment:31

FYI: optional doctests don't pass, so the package was moved to experimental.

[jdemeyer]

Changed commit from 6ff2fdf to none