#11197: Make spkg docs be built and installed after the full build
-----------------------------+----------------------------------------------
Reporter: jason | Owner: tbd
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.7
Component: packages | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Changes (by newvalueoldvalue):
* status: new => needs_review
* author: => John Palmieri
Comment:
Here's a patch for the Sage root repo (the file spkg/install). This
should perhaps be considered a first draft, because there are a few
issues/questions.
- Right now, it records a log for the docbuilding in
spkg/logs/numpy-1.5.1.p0-docs.log, for example, instead of just appending
to the already existing spkg/logs/numpy-1.5.1.p0.log. It's easy enough to
switch it around. Opinions?
- Right now, it stores a placeholder file in spkg/installed if the docs
seem to have been built correctly. (Since after building each spkg, we
delete the directory where it was built (spkg/build/numpy-...), we can't
just rely on 'make' recognizing that it's already been installed, I
think.) Is this the right way to do it?
A few things which I think belong on other tickets or which I don't know
how to solve:
- With the approach here, running "sage -i ..." or "sage -f ..." won't
install the docs. Should we add something to the sage-spkg script which
tries to build the docs if SAGE_SPKG_INSTALL_DOCS is "yes", but fails
gracefully if it can't? Or only build the docs in sage-spkg if we can
tell that the Sage library has already been installed, or some other
criterion like this? This may end up with some code duplication, or
separating out the doc-building stuff into a separate script (and then
gets us entangled in the base repo vs. scripts repo debate...).
- I noticed that the most recent cython spkg (the one in 4.7.alpha4) has
files for building the docs, at least some of which weren't added to the
Mercurial repository. I haven't checked the other spkgs for this sort of
issue, but someone should...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11197#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.
