Added comments about the doc packaging and the removal of the Doc/ tree from
the source package.
This commit is contained in:
parent
dd753eaa71
commit
c77ac1b545
14
pep-0101.txt
14
pep-0101.txt
|
@ -107,7 +107,9 @@ How to Make A Release
|
|||
- Once the branch is frozen, Fred Drake needs to create the HTML
|
||||
from the documentation. He does this and uploads the file to
|
||||
www.python.org. Then he tells Tim Peters where this file is.
|
||||
This may generate some last minute changes on the branch.
|
||||
This may generate some last minute changes on the branch. Once
|
||||
Fred is done, there can be no further checkins on the branch in
|
||||
the Doc/ directory -- not even by the RM.
|
||||
|
||||
- Tim Peters grabs the HTML and uses this to build the Windows
|
||||
installer. Tim then creates a new "release" named X.YaZ on the
|
||||
|
@ -153,9 +155,17 @@ How to Make A Release
|
|||
% cd ~
|
||||
% cvs -d <cvsroot> export -rr22a3 -d Python-2.2a3 python/dist/src
|
||||
|
||||
- Remove the documentation sources from the export; these are only
|
||||
useful to people who have LaTeX and possibly several other tools
|
||||
installed (how many tools are required depends on the
|
||||
documentation format you want to end up with). These also add
|
||||
substantially to the size of the resulting archive (almost a
|
||||
megabyte for Python 2.2).
|
||||
% rm -r Python-.2a3/Doc/
|
||||
|
||||
- Generate the tarball. Note that we're not using the `z' option
|
||||
on the tar command because 1) that's only supported by GNU tar
|
||||
as far as we know; 2) we're going to max out the compression
|
||||
as far as we know, and 2) we're going to max out the compression
|
||||
level, which isn't a supported option.
|
||||
% tar cf - Python-2.2a2 | gzip -9 > Python-2.2a2.tgz
|
||||
|
||||
|
|
Loading…
Reference in New Issue