On Thu, Aug 5, 2010 at 2:29 AM, Minh Nguyen wrote:
> Hi Fredrik,
>
> Here's a simplistic way that doesn't involve cloning or queues.
> Compile Sage from source on your machine and wrap up a binary for that
> machine with
>
> $ ./sage -bdist x.y.z-description
>
> The resulting binary then appears u
Hi Fredrik,
Here's a simplistic way that doesn't involve cloning or queues.
Compile Sage from source on your machine and wrap up a binary for that
machine with
$ ./sage -bdist x.y.z-description
The resulting binary then appears under SAGE_ROOT/dist/. Copy/move
that binary to somewhere safe so yo
Hi,
sage -clone new_branch takes 15 minutes on my "fast" laptop (and about
twice that time on my slow laptop). Nearly all that time (~14 minutes)
is spent rebuilding the entire documentation. The documentation
shouldn't change when a fresh clone is created, and Sphinx supports
updating only change
