This is to announce automake-1.18.94, a beta release. This is the second pre-release for the upcoming Automake 1.19. Please consider doing us a favour and testing it on different platforms. Special attention should be directed to the updated `make dist' mechanism.
This release has only one new feature: AM_OPTIONAL_AUTOMAKE, which lets software packages ask for `dist-XXX' formats that are built only when the matching compression tool is actually installed. Previously, the inclusion of tools not present on the host caused `make dist' to fail on systems that deliberately lack one. Everything else is important bug fixes, a number of them in `make dist' itself. There have been 18 commits by 3 people in the 8 days since 1.18.92. See the NEWS below for a brief summary. Thanks to everyone who has contributed! The following people contributed changes to this release: Kamila Szewczyk (12) Karl Berry (4) Paul Eggert (2) Download here: https://alpha.gnu.org/gnu/automake/automake-1.18.94.tar.gz https://alpha.gnu.org/gnu/automake/automake-1.18.94.tar.xz Please report bugs and problems to <[email protected]> (instead of replying to this mail), and send general comments and feedback to <[email protected]>, and patches to <[email protected]>. Thanks to everyone who has reported problems, contributed patches, and helped test Automake! -*-*-*- If you install this test release in its own prefix (recommended) and you use libtool, you'll need to arrange for the libtool m4 files to be found by aclocal. For info on this, see: https://gnu.org/s/automake/manual/automake.html#Libtool-library-used-but-LIBTOOL-is-undefined For planned incompatibilities in a possible future Automake 2.0 release, please see NEWS-future and start following the advice there now. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New in 1.19 (????-??-??): * New features added - New autoconf macro AM_OPTIONAL_AUTOMAKE. It takes a list of `dist-XXX' option names (dist-bzip2, dist-bzip3, dist-xz, dist-lzip, dist-zstd, dist-zip, dist-shar, dist-tarZ); `make dist' builds each archive when its tool is available and skips it otherwise, without making `make dist' fail. This is for systems that intentionally lack some compression tools. * Bugs fixed - Recognize COPYINGv2, COPYINGv3, COPYING.LESSERv2 and COPYING.LESSERv3 as license files; distribute them automatically, similarly to COPYING. This improves compatibility with other GNU projects, notably GNU GMP. (bug#18485) - `make dist' no longer propagates its internal distribution-directory cleanup override to recursive makes run while constructing distdir. The override could make a nested `make distcheck' leave its distribution directory behind and then fail its distclean check. - `make dist-bzip2 dist-xz' now succeeds. They share the intermediate uncompressed tarball as a result of another fix. The first goal used to delete it, so every later goal failed with ENOENT. Under GNU make the tarball is now an .INTERMEDIATE file, built once and removed once the last goal is done with it; other make implementations rebuild it per goal. (bug #10975) - Non-zero exit codes of compressors for the dist tarballs no longer abort the job in a state where the empty files are left behind. The shell redirection truncates the archive before the initial invocation, so a zero-length archive could be mistaken for a distribution; $(distdir).tar was left too. Both are now removed. This is a natural follow-up fix to bug#19614. - Busybox tar no longer assumed to be GNU tar just because it supports --version. - `make dist' now fails when tar fails, instead of exiting successfully with a truncated archive. - The filename-length-max=N option no longer rejects file names of exactly N characters; as documented, only longer ones are. (bug#81558) - The manual no longer presents 99 characters as the portable limit for file names in any archive format: it is the limit of the v7 format, whereas ustar, the default as of Automake 1.18, stores longer names. (bug#81557) - A file that is not currently present is still a part of the distribution if a `Makefile.am' rule can build it. When that rule is inside an Automake conditional, the file is distributed only when the condition is true. (bug#79049) - The `check-DEJAGNU' recipe now honors silent rules (in the non-V=1 scenario). (bug#79086) - Objective C and Objective C++ sources built with Libtool are now compiled and linked with `--tag=OBJC' and `--tag=OBJCXX', when the installed Libtool announces support for those tags (Libtool 2.6.0 and newer). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kamila Szewczyk ([email protected]) [on behalf of the automake maintainers] ================================================================== Here is the GNU automake home page: https://gnu.org/s/automake/ Here are the compressed sources: https://alpha.gnu.org/gnu/automake/automake-1.18.94.tar.gz (2.5MB) https://alpha.gnu.org/gnu/automake/automake-1.18.94.tar.xz (1.7MB) Here are the GPG detached signatures: https://alpha.gnu.org/gnu/automake/automake-1.18.94.tar.gz.sig https://alpha.gnu.org/gnu/automake/automake-1.18.94.tar.xz.sig Use a mirror for higher download bandwidth: https://www.gnu.org/order/ftp.html Here are the SHA256 and SHA3-256 checksums: File: automake-1.18.94.tar.gz SHA256 sum: 7587676af1946e7e0414f3fc1e787f112775e6e0cf1d37668a7da026512ad556 SHA3-256 sum: ee1d60917fd94f395cb33e4cd32f26cb2d77a87c53e50de37b1af2cf99e6d77f File: automake-1.18.94.tar.xz SHA256 sum: 2eb14ecb3b643c136f5e35f554116a137989c76740be52f0aea0e3926f7946a2 SHA3-256 sum: a78a4d6c287b199ddd6ec4d6c32a1559296a0c9312bb34512d4f3387189713ab Verify the SHA256 checksum with either sha256sum, sha256, or 'shasum -a 256'. Verify the SHA3-256 checksum with 'cksum -a sha3 -l 256 --base64' from coreutils-9.8. Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this: gpg --verify automake-1.18.94.tar.gz.sig automake-1.18.94.tar.gz The signature should match the fingerprint of the following key: pub rsa4096 2022-07-31 [SC] 6C22 2EA6 B2BD 216A A406 516A C868 F0B6 DE38 409D uid Kamila Szewczyk <[email protected]> uid Kamila Szewczyk <[email protected]> uid Kamila Szewczyk <[email protected]> uid Kamila Szewczyk <[email protected]> uid Kamila Szewczyk <[email protected]> uid Kamila Szewczyk <[email protected]> If that command fails because you don't have the required public key, or that public key has expired, try the following commands to retrieve or refresh it, and then rerun the 'gpg --verify' command. gpg --recv-keys 0x6C222EA6B2BD216AA406516AC868F0B6DE38409D As a last resort to find the key, you can try the official GNU keyring: wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg gpg --keyring gnu-keyring.gpg --verify automake-1.18.94.tar.gz.sig automake-1.18.94.tar.gz This release is based on the automake git repository, available as git clone https://https.git.savannah.gnu.org/git/automake.git with commit 866eab242e3506a0ffb7ac4657bdb7cd59bef773 tagged as v1.18.94. For a summary of changes and contributors, see: https://gitweb.git.savannah.gnu.org/gitweb/?p=automake.git;a=shortlog;h=v1.18.94 or run this command from a git-cloned automake directory: git shortlog v1.18.92..v1.18.94 -- With Valediction, Kamila Szewczyk (https://iczelia.net)
OpenPGP_0xC868F0B6DE38409D.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
