Rooba
/
cpython
mirror of https://github.com/python/cpython.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cpython/Doc/tools/push-docs.sh

53 lines
1.3 KiB
Bash
Raw Normal View History

Helper scripts used in published the "development" snapshots of the Python documentation.
2000-10-19 05:54:51 +00:00
#! /bin/sh
# Script to push docs from my development area to SourceForge, where the
# update-docs.sh script unpacks them into their final destination.
Update the directory names to match changes at SourceForge.
2001-05-09 16:33:34 +00:00
TARGET=python.sourceforge.net:/home/users/f/fd/fdrake/tmp
Adjust to allow an explanation of the changes to be included in the notification message.
2000-11-30 07:38:59 +00:00
Revise the scripts I use to update the documentation on the SourceForge site. These now seem (slightly) more reliable, and easier to work with since update-docs.sh no longer needs to be installed ahead of time on my account at SF.
2001-03-02 21:05:58 +00:00
ADDRESSES='python-dev@python.org doc-sig@python.org python-list@python.org'
Update publish-to-SourceForge scripts to automatically determine if the branch is the head (development) branch or a maintenance brach, and use the appropriate target directory for each.
2001-04-22 06:20:31 +00:00
VERSION=`echo '$Revision$' | sed 's/[$]Revision: \(.*\) [$]/\1/'`
EXTRA=`echo "$VERSION" | sed 's/^[0-9][0-9]*\.[0-9][0-9]*//'`
if [ "$EXTRA" ] ; then
DOCLABEL="maintenance"
DOCTYPE="maint"
else
DOCLABEL="development"
DOCTYPE="devel"
fi
Revise the scripts I use to update the documentation on the SourceForge site. These now seem (slightly) more reliable, and easier to work with since update-docs.sh no longer needs to be installed ahead of time on my account at SF.
2001-03-02 21:05:58 +00:00
EXPLANATION=''
if [ "$1" = '-m' ] ; then
EXPLANATION="$2"
shift 2
elif [ "$1" ] ; then
EXPLANATION="`cat $1`"
shift 1
Adjust to allow an explanation of the changes to be included in the notification message.
2000-11-30 07:38:59 +00:00
fi
Helper scripts used in published the "development" snapshots of the Python documentation.
2000-10-19 05:54:51 +00:00
START="`pwd`"
MYDIR="`dirname $0`"
cd "$MYDIR"
MYDIR="`pwd`"
Make this actually work now that the tool is checked in here instead of just sitting around in my working directory.
2000-10-24 19:59:55 +00:00
cd ..
Revise the scripts I use to update the documentation on the SourceForge site. These now seem (slightly) more reliable, and easier to work with since update-docs.sh no longer needs to be installed ahead of time on my account at SF.
2001-03-02 21:05:58 +00:00
# now in .../Doc/
make --no-print-directory || exit $?
make --no-print-directory bziphtml || exit $?
Helper scripts used in published the "development" snapshots of the Python documentation.
2000-10-19 05:54:51 +00:00
RELEASE=`grep '^RELEASE=' Makefile | sed 's|RELEASE=||'`
Update the helper scripts that push development docs to SourceForge; this version avoids having to build a separate authenticated connection to push the update-docs.sh script to SF.
2001-04-13 05:13:55 +00:00
PACKAGE="html-$RELEASE.tar.bz2"
scp "$PACKAGE" tools/update-docs.sh $TARGET/ || exit $?
Update publish-to-SourceForge scripts to automatically determine if the branch is the head (development) branch or a maintenance brach, and use the appropriate target directory for each.
2001-04-22 06:20:31 +00:00
ssh python.sourceforge.net tmp/update-docs.sh $DOCTYPE $PACKAGE '&&' rm tmp/update-docs.sh || exit $?
Revise the scripts I use to update the documentation on the SourceForge site. These now seem (slightly) more reliable, and easier to work with since update-docs.sh no longer needs to be installed ahead of time on my account at SF.
2001-03-02 21:05:58 +00:00
Update publish-to-SourceForge scripts to automatically determine if the branch is the head (development) branch or a maintenance brach, and use the appropriate target directory for each.
2001-04-22 06:20:31 +00:00
Mail -s "[$DOCLABEL doc updates]" $ADDRESSES <<EOF
Revise the scripts I use to update the documentation on the SourceForge site. These now seem (slightly) more reliable, and easier to work with since update-docs.sh no longer needs to be installed ahead of time on my account at SF.
2001-03-02 21:05:58 +00:00
The development version of the documentation has been updated:
Update publish-to-SourceForge scripts to automatically determine if the branch is the head (development) branch or a maintenance brach, and use the appropriate target directory for each.
2001-04-22 06:20:31 +00:00
http://python.sourceforge.net/$DOCTYPE-docs/
Revise the scripts I use to update the documentation on the SourceForge site. These now seem (slightly) more reliable, and easier to work with since update-docs.sh no longer needs to be installed ahead of time on my account at SF.
2001-03-02 21:05:58 +00:00
$EXPLANATION
EOF
exit $?