Opened 8 years ago

Last modified 4 years ago

#11197 needs_info defect

Make spkg docs be built and installed after the full build — at Version 4

Reported by: jason Owned by: tbd
Priority: major Milestone: sage-6.4
Component: build Keywords: sd32
Cc: ddrake Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by jason)

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:

Change History (4)

comment:1 Changed 8 years ago by jason

  • Description modified (diff)

comment:2 Changed 8 years ago by jason

  • Description modified (diff)

comment:3 Changed 8 years ago by jason

  • Description modified (diff)

comment:4 Changed 8 years ago by jason

  • Description modified (diff)
Note: See TracTickets for help on using tickets.