[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNASjiAB93mu0igQsiwgu=zrgu3gArMJZ+6CXHuJ+kG_ELg@mail.gmail.com>
Date: Tue, 7 Mar 2023 20:12:08 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Bastian Germann <bage@...utronix.de>
Cc: Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] kbuild: deb-pkg: default dpkg-buildpackage --build
On Tue, Mar 7, 2023 at 5:44 PM Bastian Germann <bage@...utronix.de> wrote:
>
> Am 07.03.23 um 04:21 schrieb Masahiro Yamada:
> > On Mon, Mar 6, 2023 at 8:25 AM Bastian Germann <bage@...utronix.de> wrote:
> >>
> >> deb-pkg's dpkg-buildpackage invocation was added --build=source,binary
> >> recently. Before, it relied on the default, which is
> >> --build=source,binary,all and makes no difference for the built packages
> >> as there is no "Arch: all" package.
> >
> >
> > Is this paragraph true?
> >
> > --build=source,binary,all sounds strange because
> > 'all' is contained in 'binary'.
> >
> >
> >
> > According to dpkb-buildpackage(1),
> >
> > binary = any,all
> >
> > full = source,binary = source,any,all (default)
> >
> >
> > --build=source,binary would build everything
> > even if there were 'Arch: all'.
>
> You are right. The point was that it does not change the output.
>
How do you want to rephrase this?
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists