#9465 closed enhancement (fixed)
Update to FriCAS 1.2.4
Reported by:  hemmecke  Owned by:  AlexGhitza 

Priority:  major  Milestone:  sage6.4 
Component:  packages: experimental  Keywords:  fricas 
Cc:  hemmecke, rws  Merged in:  
Authors:  Vincent Delecroix  Reviewers:  Frédéric Chapoton, Ralf Stephan 
Report Upstream:  N/A  Work issues:  
Branch:  6ff2fdf (Commits, GitHub, GitLab)  Commit:  
Dependencies:  Stopgaps: 
Description (last modified by )
The earlier upgrade is in #9354. See also #6517 for more information.
Source tarball:
http://sourceforge.net/projects/fricas/files/fricas/1.2.4/fricas1.2.4full.tar.bz2/download
that has to be renamed into fricas1.2.4.tar.bz2 (and put in $SAGE_ROOT/upstream) as usual.
Older instructions:
http://sage.math.washington.edu/home/hemmecke/pub/fricas1.1.0.spkg
http://sage.math.washington.edu/home/hemmecke/pub/fricasaldor1.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/
Change History (31)
comment:1 Changed 11 years ago by
 Cc hemmecke added
 Description modified (diff)
 Status changed from new to needs_review
comment:2 Changed 11 years ago by
 Component changed from algebra to packages
 Milestone set to sage5.0
comment:3 Changed 10 years ago by
comment:4 Changed 10 years ago by
 Status changed from needs_review to needs_work
for the record, fricas1.0.9 spkg fails to install in Sage 4.8 on x86_64 Linux (Debian).
comment:5 followup: ↓ 6 Changed 10 years ago by
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 aldorinterface 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
comment:6 in reply to: ↑ 5 Changed 10 years ago by
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 aldorinterface 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 spkginstall, I suppose).
On the other hand a fast interface to FriCAS would need an embeddable Lisp, and ECL fits this bill.
Dima
Ralf
comment:7 Changed 8 years ago by
 Milestone changed from sage5.11 to sage5.12
comment:8 Changed 8 years ago by
 Milestone changed from sage6.1 to sage6.2
comment:9 Changed 8 years ago by
 Milestone changed from sage6.2 to sage6.3
comment:10 Changed 7 years ago by
 Milestone changed from sage6.3 to sage6.4
comment:11 Changed 7 years ago by
 Component changed from packages: standard to packages: experimental
comment:12 Changed 7 years ago by
 Description modified (diff)
comment:13 Changed 7 years ago by
 Description modified (diff)
comment:14 Changed 7 years ago by
 Keywords fricas added
comment:15 Changed 7 years ago by
Hi,
Could we ship the last version ?
November 24, 2014  FriCAS 1.2.4 released.
Vincent
comment:16 Changed 7 years ago by
 Branch set to u/vdelecroix/9465
 Description modified (diff)
I wrote the spkginstall and it at least compile on my computer... If anybody want to test it
 download the source tarball
fricas1.2.4full.tar.bz2
, move it to$SAGE_ROOT/upstream
and rename itfricas1.2.4.tar.bz2
 switch to the git branch provided here
 run
sage i fricas
and thenmake
(from$SAGE_ROOT
)
I am currently trying to see whether the interface is not broken...
Vincent
comment:17 Changed 7 years ago by
 Commit set to fd76b65c59cee41a6542ca215805043454ed3055
Branch pushed to git repo; I updated commit sha1. New commits:
fd76b65  trac #9465: fricas package update

comment:18 Changed 7 years ago by
 Cc rws added
 Status changed from needs_work to needs_review
comment:19 Changed 7 years ago by
Looks like it work > needs review.
comment:20 Changed 7 years ago by
 Summary changed from Update to FriCAS 1.1.0 to Update to FriCAS 1.2.4
comment:21 Changed 7 years ago by
 Branch changed from u/vdelecroix/9465 to public/ticket/9465
 Commit changed from fd76b65c59cee41a6542ca215805043454ed3055 to 6ff2fdff73efe7828741e3457cc31621f506e97e
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

comment:22 Changed 7 years ago by
Looks good to me. If somebody else can confirm, this seems to be good to go.
comment:23 Changed 7 years ago by
 Reviewers set to Frédéric Chapoton, Ralf Stephan
 Status changed from needs_review to positive_review
Wow, fricas has Puiseux series. Builds fine. Passes all tests in interfaces
, rings
, and structure
.
comment:24 followup: ↓ 25 Changed 7 years ago by
 See also http://fricas.github.io
 What exactly is the problem with fricasaldor on 64bit machines?
 Meanwhile Aldor is under the Apache License 2.0. So fricasaldor could even install Aldor. Or there should be another spkg that installs Aldor and fricasaldor might trigger installation of Aldor, if it is not already there.
comment:25 in reply to: ↑ 24 ; followup: ↓ 26 Changed 7 years ago by
Replying to hemmecke:
 See also http://fricas.github.io
The documentation is much nicer there... why the project is both on sourceforge and github ?
 What exactly is the problem with fricasaldor on 64bit machines?
No idea... I have to try, where the source code is available ?
 Meanwhile Aldor is under the Apache License 2.0. So fricasaldor could even install Aldor. Or there should be another spkg that installs Aldor and fricasaldor 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/fricasaldor.
Vincent
comment:26 in reply to: ↑ 25 ; followup: ↓ 27 Changed 7 years ago by
Replying to vdelecroix:
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/fricassvn#fricasdevel 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.
 What exactly is the problem with fricasaldor 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 fricasaldor 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/fricasaldor.
Please do that and put me into the CC. I'm currently a little unfamiliar with Sage development.
comment:27 in reply to: ↑ 26 Changed 7 years ago by
Replying to hemmecke:
Replying to vdelecroix:
 What exactly is the problem with fricasaldor 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 fricasaldor 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/fricasaldor.
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
comment:28 Changed 7 years ago by
See #9427 for a followup ticket on integration.
comment:29 Changed 7 years ago by
No $@#$ sourceforge links the next time, please.
comment:30 Changed 7 years ago by
 Branch changed from public/ticket/9465 to 6ff2fdff73efe7828741e3457cc31621f506e97e
 Resolution set to fixed
 Status changed from positive_review to closed
comment:31 Changed 6 years ago by
 Commit 6ff2fdff73efe7828741e3457cc31621f506e97e deleted
FYI: optional doctests don't pass, so the package was moved to experimental.
Would you like to make an spkg with current Fricas? I'll make sure to review it, etc. Thanks!