mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2025-12-26 23:31:55 -08:00
Code Issues Projects Releases Wiki Activity

Mps: integrate from master: proc/release-build: use info-zip (free) for windows archives, not winzip.

Browse source 
Copied from Perforce
 Change: 158097
 ServerID: perforce.ravenbrook.com
This commit is contained in:
Richard Kistruck 2006-04-11 12:10:18 +01:00
commit e4e855c7e0
1 changed files with 29 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

34
mps/procedure/release-build/index.html
View file

@ -138,7 +138,7 @@ version/VERSION/...</code> </blockquote> </li>
</li>
<li> <p> Submit the tarball and the readme.txt file to Perforce with
the comment "Adding the MPS Kit tarball and readme.txt file for
the comment "MPS: adding the MPS Kit tarball and readme.txt file for
release RELEASE." </p> </li>
</ol>
@ -152,11 +152,25 @@ release RELEASE." </p> </li>
<li> <p> Sync the version sources to the CHANGELEVEL you determined in step 2.1. Sync the version sources to a clean area of the disk, to be sure that there are no extraneous files around. </p> </li>
<li> <p> 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. </p> </li>
<li> <p> Using the Windows file-browser, copy the version/VERSION directory, paste a copy, and rename it mps-kit-RELEASE. </p></li>
<li> <p> Make a self-extracting archive called "mps-kit-RELEASE.exe" from "mps-kit-RELEASE.zip" (in the same directory), by selcting Actions &rarr; Make .EXE File. </p> </li>
<li> <p> Use the Info-ZIP command-line utility "zip" to create a new archive of these files, called "mps-kit-RELEASE.zip" in the directory "release/RELEASE": </p>
<blockquote> <pre><code>zip -r release\RELEASE\mps-kit-RELEASE.zip mps-kit-RELEASE</code></pre> </blockquote>
</li>
<li> <p> Add the self-extracting archive and the zip file to Perforce with the comment "Adding the MPS Kit zip file for release RELEASE." </p> </li>
<li> <p> Make a self-extracting archive called "mps-kit-RELEASE.exe" from "mps-kit-RELEASE.zip" (in the same directory). The approved way to do this is to prepend the "unzipsfx.exe" extractor (here presumed to be "C:\local\bin\unzipsfx.exe"), and then adjust the offsets in the resulting file: </p>
<blockquote> <pre><code>copy /b C:\local\bin\unzipsfx.exe+release\RELEASE\mps-kit-RELEASE.zip release\RELEASE\mps-kit-RELEASE.exe
zip -A release\RELEASE\mps-kit-RELEASE.exe
</code></pre> </blockquote>
</li>
<li> <p> You can check both archives like this: </p>
<blockquote> <pre><code>unzip -tq release\RELEASE\mps-kit-RELEASE.zip
unzip -tq release\RELEASE\mps-kit-RELEASE.exe
</code></pre> </blockquote>
</li>
<li> <p> Add the zip file and the self-extracting archive to Perforce with the comment "MPS: adding the MPS Kit zip file for release RELEASE." </p> </li>
</ol>
@ -178,7 +192,7 @@ consistent with previous releases. </p></li>
the release changelevel to the <code>releases</code> table, so that the
correct set of known and fixed issues can be derived. </p></li>
<li><p> Submit these changes with the comment "Registered release
<li><p> Submit these changes with the comment "MPS: registered release
RELEASE." </p></li>
<li><p> Inform the project manager and staff by e-mail to <a
@ -265,6 +279,16 @@ href="mailto:mps-staff@ravenbrook.com">mps-staff@ravenbrook.com</a>. </p></li>
</tr>
<tr valign="top">
<td>2006-02-16</td>
<td><a href="mailto:rhsk@ravenbrook.com">RHSK</a></td>
<td>Use Info-ZIP (free) for Windows archives, not WinZip.</td>
</tr>
</table>