[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240717134459.GB24892@thelio-3990X>
Date: Wed, 17 Jul 2024 06:44:59 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
Nicolas Schier <nicolas@...sle.eu>,
"Jan Alexander Steffens (heftig)" <heftig@...hlinux.org>,
linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH v6] kbuild: add script and target to generate pacman
package
On Wed, Jul 17, 2024 at 05:34:09PM +0900, Masahiro Yamada wrote:
> On Wed, Jul 17, 2024 at 10:15 AM Nathan Chancellor <nathan@...nel.org> wrote:
> > On Tue, Jul 16, 2024 at 07:52:14PM +0200, Thomas Weißschuh wrote:
...
> > > + if [ -d "${srctree}/arch/${SRCARCH}/boot/dts" ]; then
> >
> > Does this reference to srctree...
>
>
> 'srctree' is exported by the top Makefile.
Aha, I did not realize that srctree was exported, ignore me then :)
> This is based on the assumption that we always run
> 'make pacman-pkg', and we never do 'makepkg' directly.
>
>
> Do you mean PKGBUILD should be self-contained
> so that 'makepkg' works from the command line?
No, just my misunderstanding. I think it is reasonable to tie the
PKGBUILD to the kernel tree in this manner.
Cheers,
Nathan
Powered by blists - more mailing lists