I'll try to look into the question of whether maxima can be made to work with 2.31 (or already has), but I won't have time to do so before the weekend of Feb 7.

Regards,
                Bill McCallum

On Jan 29, 2004, at 12:38 AM, Matthias Neeracher wrote:


On Jan 28, 2004, at 6:44 AM, [EMAIL PROTECTED] wrote:
May I respectfully request a new version of clisp for 10.2-gcc3.3?
Fink is at version 2.29; clisp is up to 2.32.

I did in fact have a newer clisp package ready to commit (I think it was 2.31). The problem I had was that, at least at the time, the maxima package had a bug that prevented it from working properly with clisp > 2.29, and to the best of my knowledge, that's still true today (Haven't seen a new upstream release for maxima in a long time). William, can you comment on the situation?


I'd hate to break maxima, and what little I'm using clisp itself, 2.29 worked just fine for me. Now, if there are in fact compelling reasons for you to need clisp 2.32 (other than feeling uncomfortable to be running several releases behind the latest version), then we should be able to work out a solution with keeping two different versions of clisp in the tree.

BTW, any new packages of mine will have to be 10.3 only, although they probably will work on 10.2-gcc3.3. I don't test that platform anymore.

I appreciate hearing from you and Jonathan. Knowing that there is an active user base for a package always gives me extra motivation to update it.

Matthias




_______________________________________________________ http://www.math.arizona.edu/~wmc 520 621 6697 (Work) 520 615 4569 (Home) 520 440 1729 (Mobile)



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to