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

..03-May-2022-

build-aux/H16-Mar-2013-20,27817,164

lib/H16-Mar-2013-20,76113,464

m4/H16-Mar-2013-9,4738,917

man/H16-Mar-2013-152126

po/H03-May-2022-7,7066,763

src/H16-Mar-2013-4,7363,354

tests/H16-Mar-2013-1,9541,015

.prev-versionH A D28-Dec-20125 21

.tarball-versionH A D16-Mar-20135 21

.versionH A D16-Mar-20135 21

ABOUT-NLSH A D21-Jan-201391.6 KiB1,2831,244

AUTHORSH A D28-Dec-201213 21

COPYINGH A D28-Dec-201234.3 KiB675553

ChangeLogH A D16-Mar-201328.6 KiB854618

GNUmakefileH A D16-Mar-20134.5 KiB12864

INSTALLH A D16-Mar-201315.4 KiB371289

Makefile.amH A D28-Dec-20121.8 KiB6036

Makefile.inH A D03-May-2022137.6 KiB3,4133,114

NEWSH A D16-Mar-20131.9 KiB8656

READMEH A D28-Dec-20121.1 KiB2519

README-releaseH A D16-Mar-20132.9 KiB10161

THANKSH A D28-Dec-2012408 119

TODOH A D28-Dec-20121.2 KiB3828

aclocal.m4H A D16-Mar-201343.2 KiB1,2121,113

cfg.mkH A D21-Jan-20132 KiB5522

config.hinH A D16-Mar-201333.7 KiB1,064763

configureH A D16-Mar-2013498.9 KiB18,32714,825

configure.acH A D28-Dec-20123.7 KiB10288

dist-check.mkH A D28-Dec-20125.7 KiB172134

maint.mkH A D16-Mar-201361.4 KiB1,6571,062

README

1Please glance through *all* sections of this
2`README' file before starting configuration.  Also make sure you read files
3`ABOUT-NLS' and `INSTALL' if you are not familiar with them already.
4
5GNU `cppi' adjusts or checks the indentation of C and C++ preprocessor
6directives in a file.
7
8See file `ABOUT-NLS' for how to customize this program to your language.
9See file `COPYING' for copying conditions.
10See file `INSTALL' for compilation and installation instructions.
11See file `NEWS' for a list of major changes in the current release.
12See file `THANKS' for a list of contributors.
13
14For comprehensive modifications to GNU cppi, you might need tools beyond
15those used in simple installations.  For example, you'll need gperf if
16you modify or remove cpp.gp.  Likewise, if you modify cppi.l, you'll
17need GNU flex to regenerate cppi.c.
18
19Send bug reports to `bug-cppi@gnu.org'.
20
21Your feedback will help us to make a better and more portable package.
22Consider documentation errors as bugs, and report them as such.  If you
23develop anything pertaining to `cppi' or have suggestions, let us know
24and share your findings by writing to <bug-cppi@gnu.org>.
25

README-release

1Here are most of the steps we (maintainers) follow when making a release.
2
3* Start from a clean, up-to-date git directory on "master":
4
5    make -k maintainer-clean || { ./configure && make maintainer-clean; }
6    git checkout master
7    git pull origin master
8
9* Ensure that the latest stable versions of autoconf, automake, etc.
10  are in your PATH.  See the buildreq list in bootstrap.conf for
11  the complete list of tools.
12
13* Ensure that you have no uncommitted diffs.  This should produce no
14  output:
15
16    git diff
17
18* Ensure that you've pushed all changes that belong in the release:
19
20    git push origin master
21
22* Check that the NixOS/Hydra autobuilder is reporting all is well:
23
24    http://hydra.nixos.org/jobset/gnu/cppi-master
25
26* Run the following command to download any new translations:
27
28    ./bootstrap && ./configure
29
30* Pre-release testing: ensure that the following command succeeds:
31
32    make check syntax-check distcheck
33
34* To (i) set the date, version number, and release TYPE on line 3 of
35  NEWS, (ii) commit that, and (iii) tag the release, run
36
37    # "TYPE" must be stable, beta or alpha
38    make release-commit RELEASE='X.Y TYPE'
39
40* Run the following to create release tarballs.  Your choice selects the
41  corresponding upload-to destination in the emitted gnupload command.
42  The different destinations are specified in cfg.mk.  See the definitions
43  of gnu_ftp_host-{alpha,beta,stable}.
44
45    make release RELEASE='X.Y TYPE'
46
47* Test the tarball.  Copy it to a few odd-ball systems and ensure that
48  it builds and passes all tests.
49
50* While that's happening, write the release announcement that you will
51  soon post.  Start with the template, $HOME/announce-cppi-X.Y
52  that was just created by that "make" command.
53
54Once all the builds and tests have passed,
55
56* Run the gnupload command that was suggested by your "make release"
57  run above, or run
58
59    make upload RELEASE='X.Y TYPE'
60
61* Wait a few minutes (maybe up to 30?) and then use the release URLs to
62  download all tarball/signature pairs and use gpg --verify to ensure
63  that they're all valid.
64
65* Push the NEWS-updating changes and the new tag:
66
67    v=$(cat .prev-version)
68    git push origin master tag v$v
69
70* Announce it on Savannah first, so you can include the savannah.org
71  announcement link in the email message.
72
73  Go to the news-submission form:
74
75    https://savannah.gnu.org/news/submit.php?group=cppi
76
77  If it does not work, then enable "News" for the project via this link:
78
79    https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=cppi
80
81  Write something like the following:
82
83    Subject: cppi-X.Y released [stable]
84    +verbatim+
85    ...paste the announcement here...
86    -verbatim-
87
88  Then go here to approve it:
89
90    https://savannah.gnu.org/news/approve.php?group=cppi
91
92* Send the announcement email message.
93
94* After each non-alpha release, run
95
96    make web-manual-update
97
98  to update the on-line manual accessible at
99
100    http://www.gnu.org/software/cppi/manual/
101