From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] build: add "git-dist" target for making gzipped tarballs
Date: Sun, 3 Nov 2019 03:08:06 +0000 [thread overview]
Message-ID: <20191103030806.4393-1-e@80x24.org> (raw)
Since MANIFEST is tied to files tracked by git, adding generated
files such as NEWS to that is more effort than its worth (esp.
when I'm wondering if MakeMaker is useful compared to only using
GNU make).
I also have trouble reading CamelCase, so lower-case names
are nicer and more consistent with previous releases
(which were all generated with "git archive"); but did not
include NEWS.
---
Documentation/include.mk | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/Documentation/include.mk b/Documentation/include.mk
index e948778a..04b33e4f 100644
--- a/Documentation/include.mk
+++ b/Documentation/include.mk
@@ -128,7 +128,7 @@ RELEASES =
RELEASES += v1.1.0-pre1
RELEASES += v1.0.0
-NEWS NEWS.atom NEWS.html :
+NEWS NEWS.atom NEWS.html : Documentation/include.mk
$(PERL) -I lib -w Documentation/mknews.perl $@ $(RELEASES)
# check for internal API changes:
@@ -199,3 +199,17 @@ clean :: clean-doc
pure_all ::
@if test x"$(addprefix g, make)" != xgmake; then \
echo W: gmake is currently required to build manpages; fi
+
+# No camel-cased tarballs or pathnames which MakeMaker creates,
+# this may not always be a Perl project.
+git-dist :: ver = $(shell git describe |sed -ne 's/v//p')
+git-dist :: pkgpfx := public-inbox-$(ver)
+git-dist :: NEWS
+ git archive --prefix=$(pkgpfx)/ --format=tar HEAD^{tree} >$(pkgpfx).tar
+ mkdir -p $(pkgpfx)
+ cp NEWS $(pkgpfx)/NEWS
+ $(TAR) rf $(pkgpfx).tar $(pkgpfx)/NEWS
+ $(RM) $(pkgpfx)/NEWS
+ rmdir $(pkgpfx)
+ gzip -9 $(pkgpfx).tar
+ @echo $(pkgpfx).tar.gz created
--
EW
reply other threads:[~2019-11-03 3:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191103030806.4393-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).