From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: yamada.masahiro@socionext.com, michal.lkml@markovi.net,
info@metux.net, apw@canonical.com, joe@perches.com,
linux-kbuild@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: [PATCH v1 5/5] debian: add generic rule file
Date: Fri, 8 Mar 2019 13:44:24 +0100 [thread overview]
Message-ID: <1552049064-32044-6-git-send-email-info@metux.net> (raw)
In-Reply-To: <1552049064-32044-1-git-send-email-info@metux.net>
Adding a generic debian rule file, so we can build the directly
via usual Debian package build tools (eg. git-buildpackage,
dck-buildpackage, etc). It expects the .config file already
placed in the source tree.
The rule file contains a rule for creating debian/control and
other metadata - this is done similar to the 'deb-pkg' make rule,
scripts/packaging/mkdebian.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
.gitignore | 1 +
MAINTAINERS | 6 ++++++
debian/rules | 27 +++++++++++++++++++++++++++
3 files changed, 34 insertions(+)
create mode 100755 debian/rules
diff --git a/.gitignore b/.gitignore
index a20ac26..2d8081f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -68,6 +68,7 @@ modules.builtin
# Debian directory (make deb-pkg)
#
/debian/
+!/debian/rules
#
# Snap directory (make snap-pkg)
diff --git a/MAINTAINERS b/MAINTAINERS
index 09d47cd..1edc169 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4363,6 +4363,12 @@ F: include/uapi/linux/dccp.h
F: include/linux/tfrc.h
F: net/dccp/
+DEBIAN PACKAGING FILES
+M: Enrico Weigelt <info@metux.net>
+L: linux-kbuild@vger.kernel.org
+S: Maintained
+F: debian/
+
DECnet NETWORK LAYER
W: http://linux-decnet.sourceforge.net
L: linux-decnet-user@lists.sourceforge.net
diff --git a/debian/rules b/debian/rules
new file mode 100755
index 0000000..c2f0319
--- /dev/null
+++ b/debian/rules
@@ -0,0 +1,27 @@
+#!/usr/bin/make -f
+# SPDX-License-Identifier: GPL-2.0
+
+export MAKE
+export KERNELARCH = $(shell $(MAKE) kernelarch)
+export KERNELRELEASE = $(shell $(MAKE) kernelrelease)
+export KBUILD_DEBARCH = $(shell dpkg-architecture -qDEB_HOST_ARCH)
+export KBUILD_BUILD_VERSION = $(shell $(MAKE) kernellocalversion)
+export KDEB_RULES = debian/rules.auto
+export KDEB_SOURCENAME = linux-source
+export ARCH = $(KERNELARCH)
+
+debian/control debian/changelong debian/arch debian/copyright:
+debian/control:
+ ./scripts/package/mkdebian
+
+build: debian/control
+ $(MAKE) KERNELRELEASE=$(KERNELRELEASE) ARCH=$(KERNELARCH) KBUILD_BUILD_VERSION=$(KBUILD_BUILD_VERSION) KBUILD_SRC=
+
+binary-arch: debian/control
+ $(MAKE) KERNELRELEASE=$(KERNELRELEASE) ARCH=$(KERNELARCH) KBUILD_BUILD_VERSION=$(KBUILD_BUILD_VERSION) KBUILD_SRC= intdeb-pkg
+
+clean:
+ rm -rf debian/*tmp debian/files debian/changelog debian/control debian/copyright debian/rules.auto debian/arch
+ $(MAKE) clean
+
+binary: binary-arch
--
1.9.1
next prev parent reply other threads:[~2019-03-08 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 12:44 Debian build polishing Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 1/5] Makefile: rules for printing kernel architecture and localversion Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 2/5] scripts: mkdebian: allow renaming generated debian/rules via env Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 3/5] scripts: mkdebian: fix missing dependencies Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 4/5] scripts: checkpatch.pl: don't complain that debian/rules is executable Enrico Weigelt, metux IT consult
2019-03-08 14:13 ` Joe Perches
2019-03-08 12:44 ` Enrico Weigelt, metux IT consult [this message]
2019-03-08 17:57 ` Debian build polishing Theodore Ts'o
2019-03-08 21:10 ` Enrico Weigelt, metux IT consult
2019-03-08 21:57 ` Theodore Ts'o
2019-03-10 18:50 ` Enrico Weigelt, metux IT consult
2019-03-11 16:19 ` Masahiro Yamada
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=1552049064-32044-6-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®