On Feb 16, 11:11 am, Jzmer <jzh...@gmail.com> wrote:
Hi,
> Same for me to feel sorry for my own late reply --- I thought nobody
> is gonna answer this, but I am surprised that you still remember all
> this 5 days later. Some experiment that you have suggested does churn
> out some interesting result. I checked with Sage 3.3.rc0, which ships
> jsMath v3.6a and <http://homepage.univie.ac.at/Franz.Vesely/cp_tut/
> nol2/new/c0pr_s0pr.html>, which ships jsMath v3.3c . It turns out
> that, when I did "mv ~/.fonts ~/fonts" (and did restart Firefox 3.0.6)
> the "Use Native TeX Fonts" option could be enabled on the univie
> website, but not on sagenb (jsMath v3.6a). Other than that I tried
> Epiphany 2.24.3 with gecko, which still failed to work with sagenb's
> jsMath v3.6a though.
Hmm, not sure what is at fault here, but since you have more than one
version of jsmath installed it might contribute to the problem.
> Based on the aboved experiment, I would suggest the issue should be
> with jsMath but not Firefox, as the jsMath with lower version number
> works out well. Hence, based on Tim's Debian packaging effort, I would
> say that it is probably more worthwhile not to ship sage a gigantic
> bundle, but as individual packages.
This has been discussed over and over again and it plainly doesn't
work. The Sage in Debian does not pass doctests, not even close. In
general the combinatorial explosion of configurations to debug is way
too large and it is next to impossible to find any distribution where
the version numbers even remotely match. We updated to GAP 4.4.12 in
Sage 3.3 and the doctests involving GAP will in certain files be
broken with any previous GAP release. If you used the Debian packages
for Singular Sage won't work since we patch NTL and when those NTL
libs come in conflict either Sage doesn't compile or Singular blows
up. I can go on and on and on about similar issues and that is only
the stuff I know about right on top of my head. I have never taken the
time to go out and do dumb things to break Sage :)
In the near future we plan to upgrade to a svn release of the
development version of pari and then closely track it as bugs we
report are often only fixed in pari-2.4.3svn. There is *no* way any
distribution can track this without potentially breaking other code
dependent on pari and you will be royally screwed if you want to use
pari 2.3.4 in Sage (the stable release at this point) since Sage won't
even build. We will fix all in tree code that gets broken with the new
pari-svn and push it back upstream, but until that shows up in a
distribution we will long have shipped Sage 4.0.
The way we do it is the only way and I have doubts that any
distribution packaged Sage will even be able to keep up with the
official release given that I spend working full time as the Sage
release manager :)
> Hope that this helps.
>
> Sincerely,
>
> Jing
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
