public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: Valters Jansons <valter.jansons@gmail.com>
To: location@lists.ipfire.org
Subject: [PATCH] Makefile: Bundle debian/*.manpages as EXTRA_DIST
Date: Sun, 18 Oct 2026 20:47:53 +0900	[thread overview]
Message-ID: <20261018114754.56795-1-valter.jansons@gmail.com> (raw)

Manpage building was added for Debian. This works fine in Jenkins, or if
someone pulls the source code via version control.

However, the new manpages files were not added to the release tarball.
As a result, when a version is tagged and a tarball is packaged,
attempting to build from it would fail. The builder would not be able to
determine which package each manpage should be placed into.

This commit adds d/*.manpages to EXTRA_DIST in Makefile.am, so that the
release tarball now includes these new files, and a successful build can
be done from the tarball itself.

Signed-off-by: Valters Jansons <valter.jansons@gmail.com>
---
 Makefile.am | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Makefile.am b/Makefile.am
index fb7cd2d..c74b0cc 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -1125,12 +1125,16 @@ EXTRA_DIST += \
 	debian/libloc1.install \
 	debian/libloc1.symbols \
 	debian/libloc-dev.install \
+	debian/libloc-dev.manpages \
 	debian/location.install \
+	debian/location.manpages \
 	debian/location.postinst \
 	debian/location.postrm \
 	debian/lua-location.install \
+	debian/lua-location.manpages \
 	debian/python3-location.examples \
 	debian/python3-location.install \
+	debian/python3-location.manpages \
 	debian/rules \
 	debian/source/format \
 	debian/watch
-- 
2.55.0



                 reply	other threads:[~2026-10-18 11:48 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261018114754.56795-1-valter.jansons@gmail.com \
    --to=valter.jansons@gmail.com \
    --cc=location@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox