cvxopt 1.1.8 fails to build with SAGE_SPKG_INSTALL_DOCS=yes

[strogdon]

This is because the pre-built HTML were removed, and building docs using sphinx was off.

Depends on #24972

CC: @dimpase @vbraun @haraldschilly @sagetrac-mvngu

Component: packages: standard

Keywords: spkg

Author: Leif Leonhardy, Dima Pasechnik, Jeroen Demeyer

Branch/Commit: public/14645 @ 61f5908

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/14645

[nexttime]

Diff between the .p0 and the .p1. For reference / review only.

[nexttime]

Description changed:

--- 
+++ 
@@ -1,4 +1,17 @@
 This is because the pre-built HTML docs have moved in cvxopt 1.1.6.
 
-`.p1` spkg on the way...
+---
 
+**New spkg:** [http://boxen.math.washington.edu/home/leif/Sage/spkgs/cvxopt-1.1.6.p1.spkg](http://boxen.math.washington.edu/home/leif/Sage/spkgs/cvxopt-1.1.6.p1.spkg) ([diff](https://github.com/sagemath/sage-prod/files/10657850/cvxopt-1.1.6.p0-p1.diff.gz))
+
+**md5sum:** `e2a91d60f7be040f7a09e476d642c2a2  cvxopt-1.1.6.p1.spkg`
+
+
+### cvxopt-1.1.6.p1 (Leif Leonhardy, May 25th 2013)
+* #14645: Fix installation of pre-built HTML docs (which have moved), support
+  `SAGE_SHARE`, potentially remove other old cvxopt documentation, too.
+* Run more tests in `spkg-check` (i.e., those in `src/examples/book/` as well).
+* Update / correct dependencies.
+* Minor clean-up of `spkg-check` and `spkg-install` (quoting, error checks).
+
+

[nexttime]

comment:1

Attachment: cvxopt-1.1.6.p0-p1.diff.gz

[nexttime]

Replying to @nexttime:

• Run more tests in spkg-check (i.e., those in src/examples/book/ as well).

P.S.: Tested with SAGE_CHECK=yes on Ubuntu 10.04.4 x86 and x86_64 (FSF GCC 4.7.2 and 4.8.0, respectively).

[dimpase]

comment:3

tested with SAGE_CHECK=yes on Sage 5.9 OSX10.6.8 (native lapack/blas), all good.

I understand that cvxopt docs not integrated into Sage Reference manual, but are installed in SAGE_LOCAL/share/. Wouldn't it be good to add a link somewhere in Reference manual to SAGE_LOCAL/share/ ? Otherwise it's quite hard to find, unless you know something either not really documented, IMHO.

How does one force doc building/installing? I tried

SAGE_SPKG_INSTALL_DOCS=yes sage -f cvxopt-1.1.6.p1.spkg

to no avail.

[nexttime]

comment:4

Replying to @dimpase:

I understand that cvxopt docs not integrated into Sage Reference manual, but are installed in SAGE_LOCAL/share/. Wouldn't it be good to add a link somewhere in Reference manual to SAGE_LOCAL/share/ ? Otherwise it's quite hard to find, unless you know something either not really documented, IMHO.

How does one force doc building/installing? I tried

SAGE_SPKG_INSTALL_DOCS=yes sage -f cvxopt-1.1.6.p1.spkg

to no avail.

? They're in $SAGE_ROOT/local/share/doc/cvxopt/html/, indeed probably hard to find ...

[dimpase]

comment:5

Replying to @nexttime:

Replying to @dimpase:

I understand that cvxopt docs not integrated into Sage Reference manual, but are installed in SAGE_LOCAL/share/. Wouldn't it be good to add a link somewhere in Reference manual to SAGE_LOCAL/share/ ? Otherwise it's quite hard to find, unless you know something either not really documented, IMHO.

How does one force doc building/installing? I tried

SAGE_SPKG_INSTALL_DOCS=yes sage -f cvxopt-1.1.6.p1.spkg

to no avail.

? They're in $SAGE_ROOT/local/share/doc/cvxopt/html/, indeed probably hard to find ...

I looked at the install log, and it didn't say anything :-)
Please add a message saying that docs were installed (and where to)...

[dimpase]

comment:6

Replying to @dimpase:

Wouldn't it be good to add a link somewhere in Reference manual to SAGE_LOCAL/share/ ?

rather, to SAGE_LOCAL/share/doc/, The main problem is how to add a relative link. One can in principle do ../../../../...../local/share/doc/
somewhere in doc/<LANG>/website/templates/index.html, but I'm not sure it's a good idea (IMHO the idea to put any docs in $SAGE_LOCAL/share/doc/ is not so good... )

Perhaps at least there should be a symbolic link sage/doc/local pointing there, although I'm not sure how well this works with webservers.

If this is OK then I can create a patch (hmm, but how? Does hg understand symbolic links? Or it should be in some script, this link creation?)

[dimpase]

comment:7

Harald, as this is www-related (docs structure), could you comment please?