>> * 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. So when you are saying you can develop sage you just mean you can develop the SPL? What about the framework? What about the sources of the standard spkg? That is Sage, no? >> * There is no repository for the source code (i.e. source tarball minus >> the directories spkg, devel, data, examples, local, (ipython). > > No, this is wrong. There is a repository here for that: > http://hg.sagemath.org/ > Also, a copy of the repo is included with every copy of Sage. > >> * Suppose such a repository would exist. Call it "sage-bare". > > It does exist. OK. I think there should be. >> * Add the code from http://hg.sagemath.org/scripts-main/ into the local >> directory of sage-bare and call the whole thing "sage-bootstrap". >> >> So what should sage-bootstrap (when compiled) do. > So you are talking about the existing "sage_scripts-4.1.1.spkg" spkg? Plus the files I mentioned above. I guess the reason for the sage_scripts spkg is just that it helps with "sage -upgrade", right? >> 1) (configure) Test and setup the environment (provide sage-env). >> 2) (make step: download) Consult a certain config file to figure out >> about all the other parts that are not yet on the local machine. I >> imagine that all these other parts are, in fact spkgs. The config file >> would list the spkg together with a (known good) version and some places >> where to try to download these packages from. > > Unfortunately, we cannot require internet access to build Sage. But > maybe I'm missing your point. Oh, I'm all for that. No internet at make time, but somehow sage offers to download the spkg as a service if the package is not yet found locally. It's only that what I mean here. One needs a step to pull everything together. And note that this will probably be only done by core developers, so actually, I don't care so much about whether there is Internet or not. If the packages are not there, the build fails. For a source distribution, the spkgs are already in the tarball. Ralf --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
