#9920: Ease SageNB development by providing hg commands, and extracting packages
to /devel
---------------------------+------------------------------------------------
Reporter: timdumol | Owner: jason, was
Type: defect | Status: needs_info
Priority: major | Milestone: sage-4.6
Component: notebook | Keywords:
Author: Tim Dumol | Upstream: N/A
Reviewer: Jason Grout | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Changes (by mpatel):
* status: positive_review => needs_info
Comment:
The extcode, sage_scripts, and sage packages use Mercurial in their `spkg-
install`s to merge changes into an existing repository. This could be
more efficient than copying every file every time. Can we do that here?
Does the new `spkg-install` now install SageNB two places, under `site-
packages` and `devel`? Is it practical to do just the latter?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9920#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
