From: Nathan Chancellor <nathan@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Jan Alexander Steffens (heftig)" <heftig@archlinux.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v6] kbuild: add script and target to generate pacman package
Date: Wed, 17 Jul 2024 06:44:59 -0700 [thread overview]
Message-ID: <20240717134459.GB24892@thelio-3990X> (raw)
In-Reply-To: <CAK7LNARYNqjcMkdnaY2oAkxttFTtTEgJ9VuOZOn0i4AuXp-How@mail.gmail.com>
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@kernel.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
next prev parent reply other threads:[~2024-07-17 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 17:52 Thomas Weißschuh
2024-07-17 1:15 ` Nathan Chancellor
2024-07-17 8:34 ` Masahiro Yamada
2024-07-17 8:51 ` Masahiro Yamada
2024-07-17 13:57 ` Nathan Chancellor
2024-07-17 16:33 ` Thomas Weißschuh
2024-07-17 17:18 ` Masahiro Yamada
2024-07-17 13:44 ` Nathan Chancellor [this message]
2024-07-17 13:48 ` Christian Heusel
2024-07-17 16:26 ` Thomas Weißschuh
2024-07-17 21:13 ` Nathan Chancellor
2024-07-17 18:38 ` Masahiro Yamada
2024-07-17 19:27 ` Thomas Weißschuh
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=20240717134459.GB24892@thelio-3990X \
--to=nathan@kernel.org \
--cc=heftig@archlinux.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=masahiroy@kernel.org \
--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
all inboxes | Powered by JetHome®