#11197: Make spkg docs be built and installed after the full build
-----------------------------+----------------------------------------------
Reporter: jason | Owner: tbd
Type: defect | Status: needs_info
Priority: major | Milestone: sage-4.7
Component: packages | Keywords:
Author: John Palmieri | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Changes (by jhpalmieri):
* status: needs_review => needs_info
Old description:
> Following on some concerns brought up about dependencies in building spkg
> docs, as implemented in #10823, here is a ticket for reimplementing
> #10823 so that docs are built after the full Sage build. In this way,
> spkg docs are built when the normal Sage docs are built, and we don't
> have any worries about having python or sphinx or other dependencies
> installed.
>
> From Dan's message to sage-devel:
>
> > How about, in addition to spkg-install and spkg-check, we have spkg-
> install-docs? We would move the logic that checks the
> SAGE_SPKG_INSTALL_DOCS variable to the build/install script, which would
> run the script if the env var is set. This would also allow the build
> process to determine if a spkg has documentation that can be built, using
> something roughly like tar jtf foo.spkg | grep spkg-install-docs
>
> > As a data point, doing that for all spkgs in 4.7.alpha4 (except the
> Sage library, which we handle separately) takes about 70 seconds on a
> mildly-loaded sagenb.kaist.ac.kr, which is an 8-core Xeon machine.
>
> See http://groups.google.com/group/sage-
> devel/browse_thread/thread/d46ddccff06d8670 and various tickets
> associated with #10823
>
> Here are a few updated spkgs:
>
> * numpy: #10826
> * cython: #10827
> * matplotlib: #10828
> * mpmath: #10829
> * pari: #10830
> * gap: #11198
> * python: #10831
> * sagetex: #10908
New description:
Following on some concerns brought up about dependencies in building spkg
docs, as implemented in #10823, here is a ticket for reimplementing #10823
so that docs are built after the full Sage build. In this way, spkg docs
are built when the normal Sage docs are built, and we don't have any
worries about having python or sphinx or other dependencies installed.
From Dan's message to sage-devel:
> How about, in addition to spkg-install and spkg-check, we have spkg-
install-docs? We would move the logic that checks the
SAGE_SPKG_INSTALL_DOCS variable to the build/install script, which would
run the script if the env var is set. This would also allow the build
process to determine if a spkg has documentation that can be built, using
something roughly like tar jtf foo.spkg | grep spkg-install-docs
> As a data point, doing that for all spkgs in 4.7.alpha4 (except the Sage
library, which we handle separately) takes about 70 seconds on a mildly-
loaded sagenb.kaist.ac.kr, which is an 8-core Xeon machine.
See http://groups.google.com/group/sage-
devel/browse_thread/thread/d46ddccff06d8670 and various tickets associated
with #10823
Here are a few updated spkgs:
* numpy: #10826
* cython: #10827
* matplotlib: #10828
* mpmath: #10829
* pari: #10830
* gap: #11198
* python: #10831
* sagetex: #10908
--------
Apply either
- [attachment:trac_11197-spkg-install-docs.patch] (builds docs if
environment variable SAGE_SPKG_INSTALL_DOCS is "yes"), or
- [attachment:trac_11197-spkg-install-docs.v2.patch] (adds target "spkg-
doc" to Makefile)
--
Comment:
Here's a new patch. This does the Makefile approach. I think I like the
Makefile approach, but I'm not positive, so I'm marking this as "needs
info". Please provide opinions about the two approaches and also about
the specific patches.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11197#comment:15>
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.
