Name Date Size

..29-Nov-20194 KiB

.gitignoreH A D13-Aug-2017474

.prev-versionH A D06-Jan-201911

.travis.ymlH A D06-Jan-2019311

alias-macro.plH A D13-Aug-2017844

bootstrap.shH A D06-Jan-20192 KiB

cfg.mkH A D06-Jan-20191.5 KiB

configure.acH A D13-Aug-20171.1 KiB

COPYINGH A D13-Aug-201734.3 KiB

COPYING.EXCEPTIONH A D13-Aug-20171.8 KiB

doc/H06-Jan-20194 KiB

fix-website.shH A D13-Aug-2017979

gen-authors.shH A D06-Jan-20191.7 KiB

m4/H24-Oct-201936 KiB

macro.pyH A D13-Aug-20174.3 KiB

macro2m4.pyH A D13-Aug-20171.8 KiB

macro2texi.pyH A D13-Aug-20171.8 KiB

Makefile.amH A D06-Jan-20192.3 KiB

NEWSH A D06-Jan-201946.4 KiB

README-maintH A D13-Aug-20172.5 KiB

README.mdH A D06-Jan-20192.9 KiB

rename-macro.plH A D13-Aug-20171.5 KiB

set-serial.shH A D13-Aug-2017724

TODOH A D06-Jan-201915.6 KiB

README-maint

1#+TITLE: GNU Autoconf Archive Maintainer README  -*-mode:org;fill-column:79;-*-
2#+STARTUP: showall
3
4* How to build the archive from Git.
5
6  Ensure that the following packages are installed in your system:
7
8  - Autoconf, Automake, Gnulib, and GNU Make.
9
10  - Git (1.6.x.x or later)
11
12  - Python (2.6 or later)
13
14    Python 2.6 is needed for textwrap.TextWrapper break_on_hyphens option only.
15    This is being worked on decrease python version requirements.
16
17  - texinfo (5.0 or later)
18
19  Now run the following commands:
20
21  : git clone ssh://[<login>@]git.sv.gnu.org/srv/git/autoconf-archive
22  : cd autoconf-archive
23  : ./bootstrap.sh              # set up autotools and gnulib environment
24  : ./configure                 # determine system properties
25  : make maintainer-all         # create/update all generated files that will be in a release
26  : make                        # update texinfo documentation
27
28  If "bootstrap.sh" fails because it can't find "gnulib-tool", then you should
29  clone the "gnulib" project into the top-level directory of the autoconf-archive
30  repository by running:
31
32  : git clone git://git.savannah.gnu.org/gnulib.git
33
34* How to update the web site.
35
36  Check out the web site from CVS:
37
38  : cvs -z3 -d:ext:[<login>@]cvs.savannah.gnu.org:/web/autoconf-archive co -d html autoconf-archive
39
40  Run the following commands:
41
42  : make web-manual             # generate an HTML rendering of the user documentation
43  : ./fix-website.sh            # massage file names generated by texinfo
44  :                             # copy the new files into the CVS checkout
45  : rsync -vrcH --exclude CVS --delete-after doc/manual/html/ html/
46  : (cd html ; cvs commit -m "generated from autoconf-archive $(git describe)")
47
48* How to make a release.
49
50  1. Determine the appropriate version number, i.e. today's date in ISO
51     formatting.
52
53  2. Update the date stamps in the README file.
54
55  2. Update the NEWS file. The script that generates release tarballs checks
56     that the current version number in mentioned in that file. If NEWS isn't
57     up-to-date, the script will fail.
58
59  3. Ensure that there are no uncommitted changes in 'maint' or 'master'. Then
60     create a signed tag using the naming scheme 'v<yyyy>.<mm>.<dd>'. For
61     example:
62
63     : git tag v2009.07.31 -s -m 'Autoconf Archive Version 2009.07.31'
64
65  4. Run "make stable". Other possible release types are "beta" and "major".
66
67  5. Use the command line call printed out by gnulib to upload the tarballs to
68     the GNU ftp server.
69

README.md

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