The current instructions for PIP build setup are too complicated:

---------------------------------------------------------
For 6u11 windows-i586 install builds,
to build an install that supports patch-in-place, ALT_BASE_IMAGE_DIR must be set and contain the 6u10 jre image to patch from.
Example:
ALT_BASE_IMAGE_DIR=c:/base-images.160.consumer
where ALT_BASE_IMAGE_DIR contains
jre1.6.0_10\COPYRIGHT
jre1.6.0_10\LICENSE
jre1.6.0_10\LICENSE.rtf
jre1.6.0_10\LICENSE_de.rtf
jre1.6.0_10\LICENSE_es.rtf
jre1.6.0_10\LICENSE_fr.rtf
jre1.6.0_10\LICENSE_it.rtf
jre1.6.0_10\LICENSE_ja.rtf
jre1.6.0_10\LICENSE_ko.rtf
jre1.6.0_10\LICENSE_sv.rtf
jre1.6.0_10\LICENSE_zh_CN.rtf
jre1.6.0_10\LICENSE_zh_TW.rtf
jre1.6.0_10\README.txt
jre1.6.0_10\THIRDPARTYLICENSEREADME.txt
jre1.6.0_10\Welcome.html
jre1.6.0_10\bin\*
jre1.6.0_10\lib\*
and
cksum_jre1.6.0_10
where the files may be created using the following logic:
for 6uN, where N > 10, for i = 10 to N-1
   cd to the windows 6u${i}output directory
   unzip patch-image.zip to ${ALT_BASE_IMAGE_DIR}\jre1.6.0_${i}\
   cksum patch-image.zip | awk '{print $1}' > C:\${base-images}\cksum_jre1.6.0_${i}

---------------------------------------------------------

It would be better if we had some archive somewhere of one zip file that engineers can point to for each build:

/java/re/jdk/1.6.0_11/6u11-patch-dir.zip

Our build picks it up, extracts it in the outputdir, and does the right thing. It would include the creation of checksums files, etc.