I built the Jmol .spkg simply so people could test it. What I suggest is that this .spkg be folded into the next sagenb release. I suppose if I am to help after that I will have to figure out how you are maintaining the shared code. I work regularly with SVN and CVS, but have no experience with mercurial. The mercurial model seems good, but the tools appear to be much less developed than SVN.
Jonathan On Feb 21, 1:29 pm, Volker Braun <[email protected]> wrote: > I'm all in favor of updating jmol, but I don't see the plan here. Do you > want to break out jmol from the sagenb spkg into a separate spkg? Or should > we (i.e. the sagenb maintainer) rather make a new sagenb release with the > updated jmol. > > Volker -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
