diff options
Diffstat (limited to 'binutils')
| -rw-r--r-- | binutils/README-how-to-make-a-release | 30 |
1 files changed, 12 insertions, 18 deletions
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release index 3c852c5..9e71abd 100644 --- a/binutils/README-how-to-make-a-release +++ b/binutils/README-how-to-make-a-release @@ -134,27 +134,21 @@ Approx time to complete from here: 2 hours ... Add a .dirstamp file to the gas/doc subdirectory: - touch -d <today's date> binutils-2.<release>/gas/doc/.dirstamp - tar rvf binutils-<release>.tar binutils-<release>/gas/doc/.ditstamp - rm binutils-<release>.tar.xz - xz -9 binutils-<release>.tar - - eg: - touch -d 2024-08-01 binutils-2.42.90/gas/doc/.dirstamp - tar rvf binutils-2.41.90.tar binutils-2.42.90/gas/doc/.dirstamp - rm binutils-2.42.90.tar.xz - xz -9 binutils-2.42.90.tar - + touch -d `date +%Y-%m-%d` binutils-2.43.90/gas/doc/.dirstamp + tar rvf binutils-2.43.90.tar binutils-2.43.90/gas/doc/.dirstamp + rm binutils-2.43.90.tar.xz + xz -9 -k binutils-2.43.90.tar + ...END OF FIXME c. Build a test target using this tarball. - cp binutils-2.42.90.tar.xz /dev/shm + cp binutils-*.tar.xz /dev/shm pushd /dev/shm - tar xvf binutils-2.42.90.tar.xz + tar xvf binutils-*.tar.xz mkdir build cd build - ../binutils-2.42.90/configure --quiet --enable-gold + ../binutils-*/configure --quiet --enable-gold make popd @@ -162,11 +156,11 @@ Approx time to complete from here: 2 hours ... d. Upload the pre-release snapshot to the sourceware FTP site: - scp binutils-2.42.90.tar.xz sourceware.org:/var/ftp/pub/binutils/snapshots - ssh sourceware.org sha256sum ~ftp/pub/binutils/snapshots/binutils-2.42.90.tar.xz + scp binutils-2.43.90.tar.xz sourceware.org:/var/ftp/pub/binutils/snapshots + ssh sourceware.org sha256sum ~ftp/pub/binutils/snapshots/binutils-2.43.90.tar.xz Paranoia: Compare the checksum with the local version. - + e. Clean up the source directory again. git clean -fdx @@ -193,7 +187,7 @@ Dear Translation Project binutils mailing list. Set a date for when the release will actually happen. Something like: - +------------------------------------------------------------------------ Hi Everyone, The <NEW_VERSION> branch has now been created: |