From: Jason Self <j@jxself.org>
To: linux-kbuild@vger.kernel.org
Cc: j@jxself.org
Subject: [PATCH] make builddeb invoke calls to linux-update-symlink
Date: Sat, 9 May 2020 21:06:16 -0700 [thread overview]
Message-ID: <20200510040616.2207-1-j@jxself.org> (raw)
The official Debian kernel packages, in addition to running the
scripts in /etc/kernel, also runs linux-update-symlinks via the
postinst and postrm scripts. This maintains the /vmlinuz and
/initrd.img (if it uses an initramfs) symlinks. This change makes the
builddeb script generate those same calls.
Signed-off-by: Jason Self <j@jxself.org>
---
scripts/package/builddeb | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 6df3c9f8b2da..f34c11c63ede 100755
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -195,6 +195,14 @@ export DEB_MAINT_PARAMS="\$*"
# Tell initramfs builder whether it's wanted
export INITRD=$(if_enabled_echo CONFIG_BLK_DEV_INITRD Yes No)
+$(case $script in
+postinst)
+ echo linux-update-symlinks install $version $installed_image_path
+ ;;
+postrm)
+ echo linux-update-symlinks remove $version $installed_image_path
+esac)
+
test -d $debhookdir/$script.d && run-parts --arg="$version" --arg="/$installed_image_path" $debhookdir/$script.d
exit 0
EOF
--
2.26.0
next reply other threads:[~2020-05-10 4:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 4:06 Jason Self [this message]
2020-05-22 17:01 ` [PATCH] make builddeb invoke calls to linux-update-symlink Masahiro Yamada
2020-05-23 0:41 ` Jason Self
2020-05-23 1:14 ` Ben Hutchings
2020-05-23 20:38 ` [PATCH] make builddeb invoke calls to linux-update-symlinks Jason Self
2020-05-24 0:40 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2020-05-10 3:25 [PATCH] make builddeb invoke calls to linux-update-symlink Jason Self
2020-05-10 3:49 ` Jason Self
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=20200510040616.2207-1-j@jxself.org \
--to=j@jxself.org \
--cc=linux-kbuild@vger.kernel.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