public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastian Germann <bage@linutronix.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Bastian Germann <bage@linutronix.de>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/1] builddeb: introduce profile excluding the dbg pkg
Date: Mon, 13 Mar 2023 15:17:50 +0100	[thread overview]
Message-ID: <20230313141751.186903-1-bage@linutronix.de> (raw)

Introduce a Debian build profile to exclude the massive debug package
during build. This was sent the first time as part of a patch series:
<20210411101422.7092-6-bage@linutronix.de>

Most of the patch series is included in the current work on mkdebian
but this is still missing.

A basic test showing better timing.
It is expected that the relative diff will be greater with more symbols:

make tinyconfig
# Enable CONFIG_DEBUG_INFO
time make deb-pkg
real    5m31,104s
user    4m30,960s
sys     0m46,296s

make clean
time make DPKG_FLAGS=--build-profiles=pkg.linux-upstream.nokerneldbg deb-pkg
real    5m28,076s
user    4m25,129s
sys     0m45,489s

Changelog:
v2:
 * Align the profile name with the one that ended up in Debian.
v4:
 * Prevent the creation of the dbg package when profile is set

Bastian Germann (1):
  builddeb: introduce profile excluding the dbg pkg

 scripts/package/builddeb | 4 +++-
 scripts/package/mkdebian | 1 +
 2 files changed, 4 insertions(+), 1 deletion(-)

-- 
2.39.2


             reply	other threads:[~2023-03-13 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 14:17 Bastian Germann [this message]
2023-03-13 14:17 ` [PATCH v4 1/1] builddeb: introduce profile excluding the dbg pkg Bastian Germann

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=20230313141751.186903-1-bage@linutronix.de \
    --to=bage@linutronix.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.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