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

..03-May-2022-

build-aux/H03-Feb-2012-19,47116,532

doc/H03-May-2022-3,0622,682

gnulib-tests/H03-May-2022-44,05131,910

lib/H03-May-2022-64,37743,740

libidu/H03-May-2022-6,4015,268

lisp/H03-May-2022-1,5061,394

m4/H03-Feb-2012-21,37820,115

man/H03-May-2022-2,3382,206

po/H07-May-2022-16,72414,383

src/H03-May-2022-5,2494,443

testsuite/H03-May-2022-3,9932,984

.prev-versionH A D03-Jan-20114 21

.tarball-versionH A D03-Feb-20124 21

.versionH A D03-Feb-20124 21

ABOUT-NLSH A D15-Jun-201093.1 KiB1,3281,280

AUTHORSH A D03-Jan-2011251 75

COPYINGH A D18-Sep-200834.3 KiB675553

ChangeLogH A D03-Feb-201243.5 KiB1,280956

GNUmakefileH A D28-Jan-20124.8 KiB13869

INSTALLH A D28-Jan-201215.4 KiB371289

Makefile.amH A D20-Mar-20111.1 KiB4231

Makefile.inH A D03-May-202260.8 KiB1,7731,679

NEWSH A D03-Feb-20126.8 KiB223133

READMEH A D09-Oct-20101.5 KiB3830

README-releaseH A D02-Feb-20122.9 KiB8858

THANKSH A D03-Jan-20111.7 KiB4539

TODOH A D18-Sep-20082.4 KiB6855

aclocal.m4H A D03-Feb-201245.2 KiB1,3371,228

bootstrapH A D31-Jan-201226.2 KiB896616

bootstrap.confH A D31-Jan-20123.4 KiB163118

cfg.mkH A D31-Jan-20121.8 KiB4922

configureH A D03-May-20221.1 MiB41,58231,849

configure.acH A D31-Jan-20124.2 KiB124103

dist-check.mkH A D31-Dec-20095.6 KiB171133

idutils.specH A D03-Feb-20121.8 KiB7754

idutils.spec.inH A D18-Oct-20081.8 KiB7754

maint.mkH A D28-Jan-201256 KiB1,513975

README

1This is the GNU idutils package.
2
3It provides simple, fast, high-capacity, language-independent
4identifier database tools.  Actually, the term `identifier' is too
5limiting--`mkid' stores tokens, be they program identifiers of any
6form, literal numbers, or words of human-readable text.  Database
7queries can be issued from the command-line, or from within emacs,
8serving as an augmented tags facility.
9
10`mkid' was originally written by Greg McGary <gkm@gnu.ai.mit.edu>
11and posted to comp.sources.unix in September 1987.  It was then
12maintained and enhanced by a loose knit group of programmers on the
13Internet led by Tom Horsley <Tom.Horsley@mail.hcsc.com>.  Tom released
14`mkid2' on comp.sources.unix in March, 1991.  Greg McGary resumed
15maintenance until 2000.
16
17See file `COPYING' for copying conditions.
18See file `INSTALL' for compilation and installation instructions.
19See file `NEWS' for a list of major changes in the current release.
20See file `THANKS' for a list of contributors.
21See file `TODO' for planned enhancements.
22
23For any copyright year range specified as YYYY-ZZZZ in this package
24note that the range specifies every single year in that closed interval.
25
26Mail suggestions and bug reports for these programs to
27<bug-idutils@gnu.org>.
28
29Please describe bugs completely: your input, what you expected, what you
30got, and why it is wrong.  Diffs are welcome, but please include a
31description of the problem as well, since this is sometimes difficult to
32infer.
33
34Local Variables:
35mode: text
36fill-column: 75
37End:
38

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.
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're on "master" with no uncommitted diffs.
14  This should produce no output: git checkout master; git diff
15
16* Ensure that you've pushed all changes that belong in the release
17  and that the NixOS/Hydra autobuilder is reporting all is well:
18
19    http://hydra.nixos.org/jobset/gnu/idutils-master
20
21* Run "./bootstrap && ./configure".  This downloads any new translations.
22
23* Pre-release testing:
24  Ensure that "make check syntax-check" succeeds.
25
26* Run "make distcheck"
27
28* Set the date, version number, and release type [stable/alpha/beta] on
29  line 3 of NEWS, commit that, and tag the release by running e.g.,
30
31    build-aux/do-release-commit-and-tag X.Y stable
32
33* Run the following to create release tarballs.  Your choice selects the
34  corresponding upload-to destination in the emitted gnupload command.
35  The different destinations are specified in cfg.mk.  See the definitions
36  of gnu_ftp_host-{alpha,beta,stable}.
37
38    # "TYPE" must be stable, beta or alpha
39    make TYPE
40
41* Test the tarball.  Copy it to a few odd-ball systems and ensure that
42  it builds and passes all tests.
43
44* While that's happening, write the release announcement that you will
45  soon post.  Start with the template, $HOME/announce-idutils-X.Y
46  that was just created by that "make" command.
47
48Once all the builds and tests have passed,
49
50* Run the gnupload command that was suggested by your "make stable" run above.
51
52* Wait a few minutes (maybe up to 30?) and then use the release URLs to
53  download all tarball/signature pairs and use gpg --verify to ensure
54  that they're all valid.
55
56* Push the NEWS-updating changes and the new tag:
57
58    v=$(cat .prev-version)
59    git push origin master tag v$v
60
61* Announce it on Savannah first, so you can include the preferable
62  savannah.org announcement link in the email message.
63
64  From here:
65    https://savannah.gnu.org/projects/idutils/
66  click on the "submit news", then write something like the following:
67  (If there is no such button, then enable "News" for the project via
68   the Main -> "Select Features" menu item, or via this link:
69   https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=idutils)
70
71    Subject: idutils-X.Y released [stable]
72    +verbatim+
73    ...paste the announcement here...
74    -verbatim-
75
76  Then go here to approve it:
77    https://savannah.gnu.org/news/approve.php?group=idutils
78
79* Send the announcement email message.
80
81* After each non-alpha release, update the on-line manual accessible via
82
83    http://www.gnu.org/software/idutils/manual/
84
85  by running this:
86
87    build-aux/gnu-web-doc-update
88