#8258: get "make documentation" relocation-safe
-----------------------------+----------------------------------------------
Reporter: GeorgSWeber | Owner: mvngu
Type: defect | Status: new
Priority: minor | Milestone: sage-4.3.3
Component: documentation | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by GeorgSWeber):
Hi Florent,
yes, I know that many people already put quite some effort into this, and
I know that command
{{{
sage -docbuild --update-mtimes reference html
}}}
because on my computer, it more often hangs than not.
Since its introduction, I got used to issue a "CTRL-C" every time after a
"sage-clone"; there has been more than one discussion / message thread on
sage-devel about that. But since it seems to work fine for at least some
other people (including you), I chose not to (re-)open a ticket to revert
this behaviour.
Let me say it again, this ticket here is about a slightly different issue.
You can test it easily yourself. Just take some Sage install (let's say a
Sage 4.3.2 version) of yours, do a "make" in the SAGE_ROOT directory, so
the documentation is up to date.
Then just move the Sage install to some different place in your file tree
(drag-and-drop from a GUI), i.e. create e.g. a directory "test/" side-by-
side to this Sage install, and then move this full Sage tree one level
lower in the directory hierarchy, now under "test/". No file date/time
stamps updating whatsoever, just a full plain "move". (If you wish, you
can issue "./sage" there, and you'll see some message about .pyc files to
be relocated.)
Now, issue "make" again in the SAGE_ROOT in its new location, and alas,
*all* of the documentation gets built over again.
This latter behaviour clearly exposes some basic design flaw in the way
Sphinx seems to store/interpret its metadata; at least in view of common
use cases for Sage.
(This "relocation" will happen almost certainly for anyone installing a
Sage binary distribution.)
I do think this relocation issue must be fixed. (Of course I also hope,
that in the course of doing so, more light is shed on the "sage-clone"
issues still left, but for me, that is only a second step, after this
first one.)
Cheers, Georg
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8258#comment:2>
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.
