Changes between Version 3 and Version 4 of Ticket #11197


Ignore:
Timestamp:
04/14/11 14:51:45 (9 years ago)
Author:
jason
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11197 – Description

    v3 v4  
    11Following 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.
     2
     3From Dan's message to sage-devel:
     4
     5> 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
     6
     7> 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.
     8
     9
    210
    311See http://groups.google.com/group/sage-devel/browse_thread/thread/d46ddccff06d8670 and various tickets associated with #10823
     
    513Here are a few updated spkgs:
    614
    7   * numpy: #10826
    8   * cython: #10827
    9   * matplotlib: #10828
    10   * mpmath: #10829
    11   * pari: #10830
    12   * gap: #11198
    13   * python: #10831
    14   * sagetex: #10908
     15 * numpy: #10826
     16 * cython: #10827
     17 * matplotlib: #10828
     18 * mpmath: #10829
     19 * pari: #10830
     20 * gap: #11198
     21 * python: #10831
     22 * sagetex: #10908