On Thu, 28 Jan 2010, George N. White III wrote:
> 2010/1/28 Rogério Brito <[email protected]>:
> > Package: sagemath
> > Severity: normal
> > X-Debbugs-CC: [email protected], Dan Drake <[email protected]>
> >
> > Hi, there.
> >
> > Sorry to be late on this.
> >
> > On 01/25/2010 09:52 PM, Robin Fairbairns wrote:
> >>
> >> Dan Drake <[email protected]> wrote:
> >>>
> >>> The version of Sage in Debian/Ubuntu is hopelessly outdated and right
> >>> now no one is working on getting new packages prepared. SageTeX will be
> >>> included in the next Sage released, and we can switch links and so on to
> >>> the Sage documentation.
> >>
> >> i.e., there's a .deb containing an outdated sage system? or there's
> >> no-one working to update sagetex to current ctan standards? (we know
> >> that's false.)
> >
> > I can't speak about sagetex, but sage in Debian is uninstallable in Debian's
> > sid distribution. I'm CC'ing the maintainer, via a new bug filed with
> > bugs.debian.org.
> >
> > I tried to install sagemath on my computer, since I needed to do some
> > lenghty calculations. :-(
> >
> > To be fair, it seems that the package needs some work upstream:
> >
> > http://bugs.debian.org/535357
> >
> > I don't know if the newer sources fix the problem there, but it would be
> > really nice to have this fixed before the new releases of Debian/Ubuntu.
>
> I have sagemath installed from packages under Ubuntu-9.10 and the basics
> are working. The build system seems to be reliable on mainstream
> platforms, but I'm starting to encounter python packages that won't run on
> 32-bit hardware, so I guess mainstream now means "core 2 duo". Now
> that sagetex is removed from TL, I have been installing sagetex using the
> commandline. This works, but puts everything in one directory:
>
> $ sudo sage -i sagetex-2.2.1
> [...]
> creating /usr/share/texmf/tex/generic
> creating /usr/share/texmf/tex/generic/sagetex
> copying example.pdf -> /usr/share/texmf/tex/generic/sagetex
> copying example.tex -> /usr/share/texmf/tex/generic/sagetex
> copying extractsagecode.py -> /usr/share/texmf/tex/generic/sagetex
> copying makestatic.py -> /usr/share/texmf/tex/generic/sagetex
> copying scripts.dtx -> /usr/share/texmf/tex/generic/sagetex
> copying remote-sagetex.dtx -> /usr/share/texmf/tex/generic/sagetex
> copying remote-sagetex.py -> /usr/share/texmf/tex/generic/sagetex
> copying py-and-sty.dtx -> /usr/share/texmf/tex/generic/sagetex
> copying sagetexpackage.dtx -> /usr/share/texmf/tex/generic/sagetex
> copying sagetexpackage.ins -> /usr/share/texmf/tex/generic/sagetex
> copying sagetexpackage.pdf -> /usr/share/texmf/tex/generic/sagetex
> copying sagetexparse.py -> /usr/share/texmf/tex/generic/sagetex
> copying sagetex.sty -> /usr/share/texmf/tex/generic/sagetex
>
> It would be better if the docs ended up under /usr/share/texmf/doc (or
> wherever debian thinks the doc subtree belongs. I would like
> "texdoc sagetex" to work for users.
>
> I also have sagemath installed from sources on other machines -- I
> prefer this as everything is contained in one top-level directory rather
> than getting spread around. There are so many irregularly maintained
> scientific Python packages these days, each insisting on different
> versions of scipy, etc. that a distro package manager can't cope.
Well, the challenges of keeping sagemath up to date actually have little
to do with scipy; that package in particular hasn't been a problem for me.
Instead it has been dealing with a few Python packages lagging in Python
2.6 support and making sure we have a new enough version of all the
necessary libraries.
-Tim Abbott
