On Tue, Mar 20, 2012 at 10:28 AM, Keshav Kini <keshav.k...@gmail.com> wrote: > I guess Purple Sage will have to switch to git when Sage does, since > their code bases are deeply connected. lmfdb, which I hadn't heard of > before, looks to be a separate codebase (like sagenb is). Is it > switching to git too? If not, then do we still need to ship Mercurial in > Sage to allow people to hack on lmfdb, or will they need to start using > systemwide versions of Mercurial? > > -Keshav
Actually, the code base of psage is not "deeply connected" to sage. It really is just a python library that more or less depends on "all" of sage being present. (Or at least a lot of sage.) It could probably switch to git without much of an issue. As for the LMFDB, I haven't really thought about it at all. I would like it if it used git, but I'm not going push for people to switch without much reason. I don't think Sage _needs_ to ship mercurial if it switches to git, but it would be nice for me, and probably other, if it did. As I've noted before, mercurial seems to be a PITA to build from source when I don't have root access, and the last time I tried to do it I gave up and decided to use Sage's mercurial. (git was easy to build, though.) In this (still hypothetical) situation, since most of the work has already been done, mercurial could probably also just stick around as an optional package, at least until it breaks from lack of maintenance. -- 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
