Patch from Will Sadkin

[wxWidgets.git] / wxPython / distrib / all / README.txt

diff --git a/wxPython/distrib/all/README.txt b/wxPython/distrib/all/README.txt
index 1747624dba9e5539e0a83b87048ad54b3df9f2f5..ca45b8e9aef46a97649205a6007ad2d6036eafd3 100644 (file)
--- a/wxPython/distrib/all/README.txt
+++ b/wxPython/distrib/all/README.txt
@@ -1,8 +1,8 @@
 The collection of scripts in this directory are an attempt to fully
 automate the build of the wxPython source and binary packages on all
 The collection of scripts in this directory are an attempt to fully
 automate the build of the wxPython source and binary packages on all

-build platforms.  It does this through creative use of shared folders
-on network drives, and ssh commands to the remote machines.  So this
-will likly only work in my somewhat unique environment.
+build platforms.  It does this through creative use of ssh and scp
+commands to the remote build machines, so this will likely only work
+in my somewhat unique environment.

 
 The goal here is to be able to start a build on one machine and have
 it take care of all the steps, including moving the source tarball to
 
 The goal here is to be able to start a build on one machine and have
 it take care of all the steps, including moving the source tarball to


@@ -12,7 +12,7 @@ may be copied to a public server for others to play with.
 
 Types of builds:
 
 
 Types of builds:
 

-      dry-run
+      dryrun

                Nothing extra is done with the build, this is just for
                my own testing.  
 
                Nothing extra is done with the build, this is just for
                my own testing.  
 


@@ -21,14 +21,17 @@ Types of builds:
                datestamp, and if the build is successful the results
                are copied to a daily build folder on starship.
 
                datestamp, and if the build is successful the results
                are copied to a daily build folder on starship.
 

-      release-cantidate
+      release

                The results are uploaded to the previews foler on
                starship if the build is successful.
 
 
                The results are uploaded to the previews foler on
                starship if the build is successful.
 
 

-The master script in this folder is "make-all" which will setup and
-control the whole process.  The other scripts are what are run on each
-build machine, most of which will also call out to other scripts that
-already exist, etc.
+The master script in this folder is build-all (written in Python)
+which will setup and control the whole process.  The other scripts
+(using bash) are launched from build-all either to do specific tasks
+locally, or to run on each individual build machine to manage the
+build process there, usually by calling out to other scripts that
+already exist.  The build-all script uses the taskrunner.py and
+subprocess Python modules.