From: Bastian Germann <bage@linutronix.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] kbuild: deb-pkg: default dpkg-buildpackage --build
Date: Fri, 10 Mar 2023 15:49:53 +0100 [thread overview]
Message-ID: <e89667d6-e65a-e9d8-5433-1cf918f6ff14@linutronix.de> (raw)
In-Reply-To: <CAK7LNASJeECGBiaWNjdhDbnBP3-8TKUOCXXbmbu8C9+Qa4FDxg@mail.gmail.com>
Am 10.03.23 um 15:37 schrieb Masahiro Yamada:
> If this patch is applied, 'make deb-pkg'
> would not produce the source package at all.
How so? Are you saying `make deb-pkg` never built a source package with <= 6.2?
Because those never specified a --build.
> Now I recalled the reason why I added this.
>
>
>
> dpkg-buildpackage(1):
>
> full
> Builds everything. This is an alias for source,any,all, and the
> same as the default case when no build option is specified.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
full is the default for --build. I guess the wording here is so tedious
because you can have -S, -b, -B and so on which all imply some --build.
> NACK
next prev parent reply other threads:[~2023-03-10 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 23:25 [PATCH 0/1] kbuild: deb-pkg: default dpkg-buildpackage --build Bastian Germann
2023-03-05 23:25 ` [PATCH 1/1] " Bastian Germann
2023-03-06 17:04 ` Nicolas Schier
2023-03-07 3:21 ` Masahiro Yamada
2023-03-07 8:44 ` Bastian Germann
2023-03-07 11:12 ` Masahiro Yamada
2023-03-07 11:20 ` [PATCH v2 0/1] " Bastian Germann
2023-03-07 11:20 ` [PATCH v2 1/1] " Bastian Germann
2023-03-10 14:37 ` Masahiro Yamada
2023-03-10 14:49 ` Bastian Germann [this message]
2023-03-10 15:25 ` Bastian Germann
2023-03-06 14:30 ` [PATCH 0/1] " Nicolas Schier
2023-03-06 14:36 ` 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=e89667d6-e65a-e9d8-5433-1cf918f6ff14@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 \
--cc=nicolas@fjasle.eu \
/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