On Dec 24, 6:37 am, mhampton <hampto...@gmail.com> wrote:
Hi Marshall,
> I mentioned the polymake problem a while ago, with a simple fix (just
> changing the version of cddlib it points to)
No, this is exactly the problem. You fix it so it works for the
current version, but once we change either gmp or cddlib it is broken
again and after the fix it is also broken for many previous releases.
There are also a substantial number of things plain wrong with the
spkg and it took a couple hours to do it right, but it wasn't a
priority for me, so it bitrotted.
>, and Michael wanted to do
> a more complete/automatic fix, so it rotted quietly for a while. But
> I have been installing it off and on since then by manually changing
> the spkg install. It builds fine on my intel macs after that.
The updated spkg is at #3640, so you can review it :)
> The native sage polytope functionality is improving at a pretty good
> pace now, hopefully in the next year we can do almost everything that
> polymake can. There are a number of nice things that polymake can do
> that require non-free java guis, which presumably we would never
> include anyway, so some of the remaining gaps in functionality require
> us writing new code anyway. That was one of the main reasons I
> thought it was worthwhile to work on native sage implementations.
>
> As long as I'm talking about that, could someone please review #4676?
> It didn't make it into 3.2.2 because of no review.
>
> -Marshall Hampton
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
