On Wed, Oct 14, 2009 at 4:43 PM, Ralf Hemmecke <r...@hemmecke.de> wrote: > >>> * To develop sage, one downloads the sourc tarball and then develops >>> inside the devel/sage-xyz directory. >> >> No, this is wrong. You can *definitely* develop sage by downloading >> a binary and extracting it. To modify the "sage Python library" >> involves working on devel/sage-xyz. > > Well, now we should clarify what Sage actually is. Well, I wouldn't say > that it is just the Sage Python Library. The SPL is important, but not > everything. There is framework code. The scripts are part of that but > there is also the "sage" script and a toplevel makefile. I also see > HISTORY.txt, COPYING.txt, README.txt. And they are not versioned? > Even that is not all of Sage, because there are all the standard spkgs.
In many talks I've given I say: "Sage is: 1. A distribution of free open source mathematics software, 2. Interfaces to (almost) all existing mathematics software, 3. A new library of functionality that ties everything together." So yes, Sage is more than just the Python library. > So when you are saying you can develop sage you just mean you can > develop the SPL? Yes, that is mainly what I meant. > What about the framework? > What about the sources of the standard spkg? That is Sage, no? Yes, you have to issue a command to download those. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
