#6645: [with patch, needs review] make sure bdist of sage-4.1.1 works before
release
---------------------+------------------------------------------------------
Reporter: was | Owner: tbd
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.1.1
Component: build | Keywords:
Reviewer: | Author:
Merged: |
---------------------+------------------------------------------------------
Comment(by mvngu):
Here are the steps I went through to test the proposed solution:
1. Take the source tarball of Sage 4.1.1.rc2 and compile that version.
1. Once the compilation has finished, build the HTML version of the
documentation with
{{{
./sage -docbuild all html
}}}
1. Apply the patch `trac_6645-scripts_doctest.patch` to the script
repository in `SAGE_ROOT/local/bin`.
1. Manually patch the file `SAGE_ROOT/spkg/install` with the patch
`trac_6645-spkg_install.patch`.
1. Make an experimental source distribution and call it, say,
sage-4.1.1-exp using the command
{{{
./sage -sdist 4.1.1-exp
}}}
The new experimental source distribution can be found in
`SAGE_ROOT/dist`.
1. Uncompress the tarball of that source distribution and compile it.
1. Once the compilation has finished, build the HTML version of the
documentation using `./sage -docbuild all html`.
1. Make a binary distribution of the newly compiled experimental source
distribution, with the command
{{{
./sage -bdist 4.1.1-exp
}}}
The binary version can be found in `SAGE_ROOT/dist`.
1. Uncompress the binary tarball and run the binary version. Then exit
Sage and run Sage again with
{{{
./sage -br main
}}}
Quit Sage again, and now do
{{{
make test
}}}
Notice that the documentation wouldn't rebuild when running the test
suite with the latter command.
1. Here comes a show-stopper: Wait for the test suite to finish or just
preempt it with control-C. Manually rebuild the documentation with `./sage
-docbuild all html`. Once the HTML version of the documentation has
finished building, now run the test suite again with `make test`. This
time, running the test suite would also rebuild the documentation.
1. Wait for the documentation to finish rebuilding so that the test suite
would proceed. When the test suite starts running, you can let it finish
or again you can preempt it with control-C. If you run the test suite a
third time with `make test`, the documentation won't rebuild this time;
the rebuild of the documentation would be skipped over and the test suite
would proceed.
1. But if you manually rebuild the documentation again with `./sage
-docbuild all html`, then the HTML version of the documentation would be
rebuilt as requested. This is interesting because we have already manually
rebuilt the HTML version of the documentation.
[[BR]]
The upshot is that manually rebuilding the HTML version of the
documentation would also cause the documentation to be rebuilt when
running the test suite with `make test`. But if you run the test suite
with the latter command, then requesting a manual build of the
documentation would be done as requested, regardless of whether or not the
documentation has been built.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6645#comment:7>
Sage <http://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
-~----------~----~----~----~------~----~------~--~---
