From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com, nab <nabijaczleweli@nabijaczleweli.xyz>,
"G . Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: [RFC 0/3] Prepare the Makefile and scripts/ for releasing
Date: Sat, 16 Apr 2022 01:30:45 +0200 [thread overview]
Message-ID: <20220415233048.70477-1-alx.manpages@gmail.com> (raw)
Hi!
I'm preparing the Makefile and scripts to be able to release
without hidden scripts, just from the repository. I put in the
Makefile everything that can be done incrementally (or at least
idempotently, since tar(1) doesn't really allow incrementally
creating an archive, unlike ar(1)), and in scripts what can't
(i.e., the COLOPHON generation).
I tried to follow conventions (from GNU and others) as much as
possible.
The COLOPHON format was kept as I see it in existing pages in my
system, with one difference: until now, the URI in the COLOPHON
wasn't being enclosed in <> (the script didn't use .UR/.UE).
I fixed that.
Now one can generate DISTFILES (.tar, .tar.gz, and .tar.xz files)
simply with the following commands. The version number is taken
from git.
./scripts/append_COLOPHON.sh
make dist-gz
Of course, the generation of the COLOPHON is not a dependency for
the generation of the tarballs, but it's likely that both commands
will be run together.
Cheers,
Alex
Alejandro Colomar (3):
scripts/remove_COLOPHON.sh: Allow passing directories to the script
scripts/append_COLOPHON.sh: Add script to append the COLOPHON section
Makefile: dist: Add target to create distribution archives
Makefile | 49 ++++++++++++++++++++++++++++++++++++++
scripts/append_COLOPHON.sh | 38 +++++++++++++++++++++++++++++
scripts/remove_COLOPHON.sh | 6 ++---
3 files changed, 90 insertions(+), 3 deletions(-)
create mode 100755 scripts/append_COLOPHON.sh
--
2.30.2
next reply other threads:[~2022-04-15 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 23:30 Alejandro Colomar [this message]
2022-04-15 23:30 ` [PATCH 1/3] scripts/remove_COLOPHON.sh: Allow passing directories to the script Alejandro Colomar
2022-04-15 23:30 ` [PATCH 2/3] scripts/append_COLOPHON.sh: Add script to append the COLOPHON section Alejandro Colomar
2022-04-15 23:30 ` [PATCH 3/3] Makefile: dist: Add target to create distribution archives Alejandro Colomar
2022-04-16 13:02 ` [RFC v3 " Alejandro Colomar
2022-04-15 23:33 ` [RFC 0/3] Prepare the Makefile and scripts/ for releasing Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220415233048.70477-1-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox