From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
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 18:33:27 +0200 [thread overview]
Message-ID: <41cf1da7-ef13-4586-9e9a-f1f8f3b34d8e@t-8ch.de> (raw)
In-Reply-To: <20240717135747.GC24892@thelio-3990X>
On 2024-07-17 06:57:47+0000, Nathan Chancellor wrote:
> On Wed, Jul 17, 2024 at 05:51:21PM +0900, Masahiro Yamada wrote:
> ...
> > > > > diff --git a/scripts/package/PKGBUILD b/scripts/package/PKGBUILD
> > > > > new file mode 100644
> > > > > index 000000000000..eb3957fad915
> > > > > --- /dev/null
> > > > > +++ b/scripts/package/PKGBUILD
> > > > > @@ -0,0 +1,99 @@
> > > > > +# SPDX-License-Identifier: GPL-2.0-only
> > > > > +# Maintainer: Thomas Weißschuh <linux@weissschuh.net>
> > > > > +# Contributor: Jan Alexander Steffens (heftig) <heftig@archlinux.org>
> > > > > +
> > > > > +pkgbase=linux-upstream
> ...
> > Perhaps, this may make sense.
> >
> > Currently,
> > pkgname=("${pkgbase}" "${pkgbase}-headers" "${pkgbase}-api-headers")
> > is hard-coded.
> >
> > I do not think linux-upstream-headers make sense
> > when CONFIG_MODULE is disabled.
> >
> > scripts/package/mkspec turns off with_devel
> > when CONFIG_MODULE is disabled.
Ack.
> Yes, I think that is a reasonable change to make. In the face of that
> potential change, would it make sense to slightly adjust the
> makedepends? pahole is only needed when CONFIG_DEBUG_INFO_BTF is enabled
> but I guess no other package building infrastructure makes dependencies
> conditional in that manner.
The pahole dependency optimization seems like an overcomplication.
Arch Linux in general is not hell-bent on minimizing dependencies,
for example there are no dev-packages at all.
Also if the kernel will require pahole in more cases it will create
churn.
> Another thing I wonder about would be allowing the user to customize the
> value of pkgbase, like
>
> pkgbase=${PACMAN_PKGBASE:-linux-upstream}
>
> because unlike Debian and Fedora, multiple versions of the same kernel
> package cannot be installed at once. If I wanted to build a package
> against mainline and -next and install them side by side, I could only
> do so if they are named differently. This would allow one to provide
> PACMAN_PKGBASE=linux-mainline and PACMAN_PKGBASE=linux-next to
> accomplish that. Might be a hyper specific use case though, so I am not
> opposed to disregarding it.
Ack.
FYI linux-upstream was picked to be consistent with pkg-debian and not
to conflict with the existing linux-mainline package in AUR [0].
[0] https://aur.archlinux.org/packages/linux-mainline
next prev parent reply other threads:[~2024-07-17 16:33 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 [this message]
2024-07-17 17:18 ` Masahiro Yamada
2024-07-17 13:44 ` Nathan Chancellor
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=41cf1da7-ef13-4586-9e9a-f1f8f3b34d8e@t-8ch.de \
--to=linux@weissschuh.net \
--cc=heftig@archlinux.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@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®