#14556: The maxima spkg has cruft dating back to days of clisp use
------------------------------------------------+---------------------------
Reporter: Snark | Owner: jdemeyer
Type: enhancement | Status: closed
Priority: minor | Milestone: sage-5.10
Component: packages: standard | Resolution: fixed
Keywords: noreadline | Work issues:
Report Upstream: N/A | Reviewers: Jeroen
Demeyer, Julien Puydt
Authors: Julien Puydt, Jeroen Demeyer | Merged in:
sage-5.10.beta5
Dependencies: | Stopgaps:
------------------------------------------------+---------------------------
Comment (by kcrisman):
Replying to [comment:20 kcrisman]:
> > It is quite weird. But I assume this is material for a new ticket now,
is it the full log for maxima? If you have more before that I think we
should inspect it.
> The rest of the log is completely ordinary, same as always. At this
point I'm just asking for someone else to test upgrading for this spkg.
>
> Indeed,
> {{{
> $ ls spkg/build/maxima-5.29.1.p3/src/src/binary-ecl/
> maxima-package.c maxima-package.data maxima-package.eclh
> }}}
Weirdly, now as I try to reinstall the p1 spkg, I get the same problem! Of
course, it doesn't show up on the screen, but in error.log it's there, and
the `binary-ecl` folder has the same three files.
Is it possible we have to touch ecl first so that it upgrades when
upgrading this? I don't see why, but I'll try that next.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14556#comment:21>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
