> I am not aware of any SPEC or SRPM for Sage though there might be SPECs for > several components of Sage out there. The only somewhat active packaging > efforts for the whole of Sage we are aware of are: > > - Debianhttp://wiki.sagemath.org/DebianSAGE > - someone on IRC is packaging Sage for Pardus Linux (this distribution has its > own package format)
Thank you for letting me know. I will keep an eye out for these as I'm progressing along on my side. > 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. --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
