On Thu, Feb 9, 2012 at 7:53 AM, Jason Grout <jason-s...@creativetrax.com> wrote: > On 2/9/12 9:44 AM, Keshav Kini wrote: >> >> On Thu, Feb 9, 2012 at 23:30, Jason Grout<jason-s...@creativetrax.com> >> wrote: >>> >>> I use separate directories in devel/ to have multiple versions of the new >>> sage notebook installed. They're almost all git repositories, though :). >>> I >>> don't know if that counts as a yes or no to your question. >> >> >> IMO it's important to note that these directories and the symlink are >> managed by you (afaik), and are not ingrained into Sage's concept of >> what is there. This is in contrast to the Sage library, which actually >> causes Sage to refuse to start up unless there is a symlink >> $SAGE_ROOT/devel/sage pointing to a directory called >> $SAGE_ROOT/devel/sage-foo (as I discovered when writing >> https://github.com/sagemath/sagelib/blob/github-master/README.rst ). >> So I think that counts as a "no", if the question is to be interpreted >> as being about whether we should keep that "branch"-handling code in >> the Sage scripts. Though of course I don't know whether John meant it >> that way. > > > You correctly interpreted my response, and I agree with your conclusions. I > haven't used the sage branch-handling code in years.
I used them extensively when (1) I was working on my thesis, and wanted a set of patches (possibly corresponding to several tickets) separate from my other development and (2) when working on coercion, where rebuilding all the Cython code was painful if I pushed/popped a patch touching parent.pxd and (3) to have a pristine base on which to referee tickets (without having to disturb anything else I'm working on). I suppose some people simply have multiple copies of Sage itself lying around... Another important user, though this could be handled as a special case, is the patchbot. It creates a new "symlink branch" for each ticket, and when re-visiting a ticket it doesn't have to re-apply/rebuild except for what changed. As rebuilding is cheaper than testing for most changes, I suppose we could throw away this work every time, but it was a precursor to the next phase of the patchbot which would be a sage notebook server that would allow you to start worksheets in any one of the branches (simultaneously) to actually play with the code. Perhaps, with some agressive caching mechanisms like ccache, we could do this cloning at a higher level (and then then handle spkgs in the patchbot as well). This would fit in well with the vision of having a single top-level repository that contains everything except the pristine upstream source tarballs, and "installing" an spkg is a matter of submitting a patch to change a reference and re-building. - Robert -- 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
