drop configure~ (backup) from git and tarballs?

Unbound
1

Hi!

Maybe it's a good idea to avoid storing configure~ (the backup) in
git and in the release tarballs?

I'd say configure should not be in git too, but this is questionable.
For configure~, things should be clear, no?

BTW, in 1.24 release, there's mention of usage of sphinx to generate
the manpages, but each of README.md and docs/README.man refers to
each other for instructions without providing ones :slight_smile:

Thanks,

/mjt

2

Hi Michael,

That files should not be in the release tarball of course. A fix is in https://github.com/NLnetLabs/unbound/commit/8419e9780e9775e91842a546bbddde542a557bd6 .

That would not have the configure~ file in upcoming release tarballs.

Best regards, Wouter

3

Hi Michael!

BTW, in 1.24 release, there's mention of usage of sphinx to generate
the manpages, but each of README.md and docs/README.man refers to
each other for instructions without providing ones :slight_smile:

I updated the text in the README.man [1] with a clearer explanation hopefully.
README.man is supposed to point to the documentation repository [2] for further instructions.

But as pointed out in the above commit, this is mostly for developers.
The <man-page.number>.in files are the manpages in generated troff and they are the ones which will be used for man page installation, same as always.

Best regards,
-- Yorgos

[1] https://github.com/NLnetLabs/unbound/commit/3017a0aa52dc7d13e08b85c5124993f8660bc162
[2] https://github.com/NLnetLabs/unbound-manual