diff options
| author | Paul Smith <psmith@gnu.org> | 2006-04-01 06:36:40 +0000 |
|---|---|---|
| committer | Paul Smith <psmith@gnu.org> | 2006-04-01 06:36:40 +0000 |
| commit | a8f101d0bc354896e410e218db12b449b0447de7 (patch) | |
| tree | b161fc78e688e2c08828116dca05cb148af6e305 /README.cvs | |
| parent | 367a49591e2b2335f3f5b42e290651d4df77e933 (diff) | |
| download | gunmake-a8f101d0bc354896e410e218db12b449b0447de7.tar.gz | |
Release GNU make 3.81.
Update NEWS docs.
Enhance the manual to use automake version.texi, and use the canonical
FSF copyright features and statement.
Some $(realpath ...) tests won't work on Windows; leave them out
The jobserver filedescriptor test might fail if some FDs are reserved,
so for now comment out that check.
Diffstat (limited to 'README.cvs')
| -rw-r--r-- | README.cvs | 14 |
1 files changed, 10 insertions, 4 deletions
@@ -45,6 +45,11 @@ Gettext, and any tools that those utilities require (GNU m4, Perl, etc.). See the configure.in file to find the minimum versions of each of these tools. You will also need a copy of wget. +When building from CVS you must build in the source directory: "VPATH +builds" from remote directories are not supported. Once you've created +a distribution, of course, you can unpack it and do a VPATH build from +there. + After checking out the code, you will need to perform these steps to get to the point where you can run "make". @@ -127,8 +132,6 @@ before making an official release: * Update the configure.in file with the new release number. * Update the NEWS file with the release number and date. - * Update the doc/make.texi file with the release number and date. - Check the variables EDITION, VERSION, UPDATED, and UPDATE-MONTH. * Create the new release in the Savannah "Bugs" Administration for both the "Component Version" and "Fixed Release" fields. * Create the new release in the Savannah "Patches" Administration for @@ -169,8 +172,11 @@ It will ask for the GPG passphrase _THREE_ times. Sigh. Where to Announce ----------------- -Create the announcement in a text file, then sign it with GPG. Upload -to gnu.org, then login and send from my account there. +Create the announcement in a text file, then sign it with GPG. + + gpg --clearsign <announcement.txt> + +Upload to gnu.org, then login and send from my account there. Email to: make-alpha@gnu.org, bug-make@gnu.org, help-make@gnu.org, make-w32@gnu.org. Email to: info-gnu@gnu.org |