about summary refs log tree commit homepage
path: root/Documentation
diff options
authorEric Wong <e@80x24.org>2019-11-03 02:53:39 +0000
committerEric Wong <e@80x24.org>2019-11-03 02:53:39 +0000
commit70ebd82066a0c9c4c92579c07b7d0e36bbb4870a (patch)
tree09952764192a992effe504b61571a325fb6fb82a /Documentation
parent8edf9493a92f53a5135b9d36f5e913b46d6486c8 (diff)
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.
Diffstat (limited to 'Documentation')
1 files changed, 15 insertions, 1 deletions
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