From ba680615003e39f08b06c4dd85e4e1b84c525f74 Mon Sep 17 00:00:00 2001 From: Nick Barnes Date: Wed, 19 Jun 2002 14:34:51 +0100 Subject: [PATCH] Improved release build procedure and readme based on experience of release 1.100.0. Copied from Perforce Change: 30301 ServerID: perforce.ravenbrook.com --- mps/procedure/release-build/index.html | 36 +++++++++++++++++++++----- mps/readme.txt | 6 +++-- 2 files changed, 34 insertions(+), 8 deletions(-) diff --git a/mps/procedure/release-build/index.html b/mps/procedure/release-build/index.html index bd36a95bcff..71da8901181 100644 --- a/mps/procedure/release-build/index.html +++ b/mps/procedure/release-build/index.html @@ -97,24 +97,38 @@ change to get it.

  • -

    Create a tarball containing the MPS sources:

    +

    Create a tarball containing the MPS sources, and open it for add:

    cp -r version/VERSION mps-kit-RELEASE
    + mkdir -p release/RELEASE
    tar cf - mps-kit-RELEASE | gzip -c > release/RELEASE/mps-kit-RELEASE.tar.gz
    - rm -r mps-kit-RELEASE + rm -r mps-kit-RELEASE
    + p4 add release/RELEASE/mps-kit-RELEASE.tar.gz
    • -

  • Add the tarball to Perforce with the comment "Adding the MPS Kit tarball for release RELEASE."

    • +
  • + +

    Add the readme.txt file to the release directory:

    + +
    + p4 integrate version/VERSION/readme.txt release/RELEASE/readme.txt +
    + +
    • + +

  • Submit the tarball and the readme.txt file to Perforce with +the comment "Adding the MPS Kit tarball and readme.txt file for +release RELEASE."

    • 2.3. MPS Kit Zip file

    -

    On a Window box:

    +

    On a Microsoft Windows box:

      @@ -122,9 +136,9 @@ change to get it.

    1. Launch WinZip and create a new archive called "mps-kit-RELEASE.zip" in the directory "release/RELEASE". Add the MPS sources by selecting "version/VERSION" and turning on "Include subfolders" option.

      2. -

    2. Make a self-extracting archive called "mps-kit-RELEASE.exe" from "mps-kit-RELEASE.zip" (in the same directory), by selcting Actions → Make .EXE File. Specify the default "unzip to" folder as "mps-kit-RELEASE".

      3. +

    3. Make a self-extracting archive called "mps-kit-RELEASE.exe" from "mps-kit-RELEASE.zip" (in the same directory), by selcting Actions → Make .EXE File.

      4. -

    4. Add the self-extracting archive to Perforce with the comment "Adding the MPS Kit zip file for release RELEASE."

      5. +

    5. Add the self-extracting archive and the zip file to Perforce with the comment "Adding the MPS Kit zip file for release RELEASE."

    @@ -193,6 +207,16 @@ href="mailto:mps-staff@ravenbrook.com">mps-staff@ravenbrook.com.

    + + + 2002-06-19 + + NB + + Fixed up based on experience of release 1.100.0. + + + diff --git a/mps/readme.txt b/mps/readme.txt index 49c58a74ceb..21ed02f542b 100644 --- a/mps/readme.txt +++ b/mps/readme.txt @@ -53,8 +53,9 @@ This document is not confidential. The MPS Kit is a complete set of sources and documentation to enable third parties to use, modify, and adapt the MPS. -For Windows, the kit is distributed as the ZIP archive -"mps-kit-1.100.0.zip". Unpack it using WinZip. +For Windows, the kit is distributed as the self-extracting archive +"mps-kit-1.100.0.exe", and also as the ZIP archive +"mps-kit-1.100.0.zip", which may be unpacked using WinZip. For Unix and Mac OS X, the integration kit is distributed as the tarball "mps-kit-1.100.0.tar.gz". Unpack it using the command "gunzip -c @@ -250,6 +251,7 @@ B. DOCUMENT HISTORY 2002-05-20 RB Created based on template from P4DTI project. 2002-06-18 NB Minor updates and corrections. 2002-06-18 RB Removed obsolete requirement for MASM. +2002-06-19 NB Added note on self-extracting archive C. COPYRIGHT AND LICENSE