William Stein <wst...@gmail.com> writes: > Hi Keshav (et al.), > > I think the reason I implemented the kludgy "sage -clone" Sage branch > thing (way back in maybe March 2006) was because we had no dependency > checking for Pyrex files. Now that we have dependency checking, > lightweight branching should be able to accomplish the same thing much > more efficiently, right?
Well, I normally wouldn't write this contentless response, but since you've addressed me specifically: I have no idea how Cython works, it all seems like magic to me :) So I have no idea whether there's some problem with getting rid of `sage -clone`. But even if not, then I think it's Cython which needs to be fixed. `sage -clone` should not exist, IMO. We should be able to put whatever we want at $SAGE_ROOT/devel/sage, whether it be a symlink to some other directory, or just a directory itself, and expect Sage to read its library from there. Sage should not know or care about where a symlink at $SAGE_ROOT/devel/sage points to. But since you're calling it a kludge, I guess you agree with me on this. :) -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- 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
