On Dec 17, 2007 9:51 AM, gri6507 <[EMAIL PROTECTED]> wrote: > > However, we - I think I can speak for all the Sage developers here - are > > very > > eager to get Sage into Linux distributions so we will help as much as > > possible. > > > > So please report back if you run into any trouble. > > I have actually found a solution for this one already, but I thought > I'd ask here anyways. Is there a reason why the Makefile in devel/doc > defaults to PYTHON=python (the python already in the path) instead of > sage-python (the python just build for sage?). This is actually a > problem for creating documentation. So, in my SPEC file, I have > explicitly modify the Makefile to redefine PYTHON.
The Sage documentation build system started by me copying verbatim from the *Python* doc directory that comes with Python itself. Basically I just adapted what is done by Python to Sage. There are surely many ways in which this can be improved and what you suggest above is one of them. Thanks! Send me off-list a request for a trac login/password, so you can post to the Sage trac server with each fix you find for the sage documentation system. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
