• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

build-aux/H05-Jan-2019-11,75110,456

doc/H05-Jan-2019-65,52348,142

m4/H05-Jan-2019-57,46752,996

.tarball-versionH A D05-Jan-201911 21

AUTHORSH A D05-Jan-20196 KiB381379

COPYINGH A D05-Jan-201934.3 KiB675553

COPYING.EXCEPTIONH A D05-Jan-20191.8 KiB4432

ChangeLogH A D05-Jan-2019230.8 KiB6,7104,278

INSTALLH A D05-Jan-201915.4 KiB371289

Makefile.amH A D05-Jan-20192.3 KiB5029

Makefile.inH A D05-Jan-201928.7 KiB869756

NEWSH A D05-Jan-201946.4 KiB1,064739

READMEH A D05-Jan-20192.9 KiB6850

TODOH A D05-Jan-201915.6 KiB279255

aclocal.m4H A D05-Jan-201926.7 KiB741667

configureH A D05-Jan-2019132.6 KiB3,5882,885

configure.acH A D05-Jan-20191.1 KiB3225

README

1Autoconf Archive
2================
3
4The GNU Autoconf Archive is a collection of more than 500 macros for [GNU
5Autoconf](https://www.gnu.org/software/autoconf) that have been contributed
6as free software by friendly supporters of the cause from all over the
7Internet. Every single one of those macros can be re-used without imposing
8any restrictions whatsoever on the licensing of the generated configure
9script. In particular, it is possible to use all those macros in configure
10scripts that are meant for non-free software. This policy is unusual for a
11Free Software Foundation project. The FSF firmly believes that software
12ought to be free, and software licenses like the GPL are specifically
13designed to ensure that derivative work based on free software must be
14free as well. In case of Autoconf, however, an exception has been made,
15because Autoconf is at such a pivotal position in the software development
16tool chain that the benefits from having this tool available as widely as
17possible outweigh the disadvantage that some authors may choose to use it,
18too, for proprietary software.
19
20The best place to start exploring the Archive is the [on-line
21documentation](https://www.gnu.org/software/autoconf-archive/). There is
22also the [Autoconf Archive home
23page](http://savannah.gnu.org/projects/autoconf-archive/) at Savannah and
24a [Github mirror](https://github.com/autoconf-archive/autoconf-archive).
25
26Downloads
27---------
28
29Here are the compressed sources:
30
31-   <http://ftpmirror.gnu.org/autoconf-archive/autoconf-archive-2019.01.06.tar.xz>
32
33Here are the GPG detached signatures:
34
35-   <http://ftpmirror.gnu.org/autoconf-archive/autoconf-archive-2019.01.06.tar.xz.sig>
36
37You can use either of the above signature files to verify that the
38corresponding file (without the .sig suffix) is intact. First, be sure
39to download both the .sig file and the corresponding tarball. Then, run
40a command like this:
41
42    gpg --verify autoconf-archive-2019.01.06.tar.xz.sig
43
44If that command fails because you don't have the required public key,
45then run this command to import it:
46
47    gpg --keyserver keys.gnupg.net --recv-keys 99089D72
48
49and rerun the `gpg --verify` command.
50
51License
52-------
53
54Copyright (c) 2019 Autoconf Archive Maintainers \<<autoconf-archive-maintainers@gnu.org>\>
55
56The GNU Autoconf Archive is free software: you can redistribute it and/or
57modify it under the terms of the GNU General Public License as published
58by the Free Software Foundation, either version 3 of the License, or (at
59your option) any later version.
60
61The GNU Autoconf Archive is distributed in the hope that it will be
62useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
63MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
64Public License for more details.
65
66You should have received a copy of the GNU General Public License along
67with the GNU Autoconf Archive. If not, see <https://www.gnu.org/licenses/>.
68