From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH 0/4] dist-kernel: Improved kernel version logic, take two
Date: Wed, 26 Oct 2022 13:31:36 +0200 [thread overview]
Message-ID: <20221026113140.3213-1-mgorny@gentoo.org> (raw)
Hi,
The previous attempt to improve version handling in dist-kernel eclasses
turned out not to work for live ebuilds. Let's try a different approach
that:
1) uses ${PV}${KV_LOCALVERSION} for /usr/src/linux-* directory
(i.e. "6.0_rc1-gentoo-dist" or "5.15.9999-dist") because it's
the simplest approach
2) grabs the version from the "release" file for /lib/modules directory
(i.e. "6.0.0-rc1-gentoo-dist" or "5.15.74-dist") because that should
easily handle all the corner cases, including live ebuilds and custom
configs
3) uses the transformed version for the pkg_preinst() version check
in non-live ebuilds because that should be good enough to verify
that we did not fail to bump genpatches version
Michał Górny (4):
kernel-build.eclass: Revert "Respect KV_FULL"
kernel-install.eclass: Revert "Add KV_FULL [...]"
kernel-install.eclass: Account for PV/KV mismatch
kernel-build.eclass: Account for PV/KV mismatch
eclass/kernel-build.eclass | 45 ++++++++++-------
eclass/kernel-install.eclass | 93 ++++++++++++++++++++----------------
2 files changed, 78 insertions(+), 60 deletions(-)
--
2.38.1
next reply other threads:[~2022-10-26 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 11:31 Michał Górny [this message]
2022-10-26 11:31 ` [gentoo-dev] [PATCH 1/4] kernel-build.eclass: Revert "Respect KV_FULL" Michał Górny
2022-10-26 11:31 ` [gentoo-dev] [PATCH 2/4] kernel-install.eclass: Revert "Add KV_FULL [...]" Michał Górny
2022-10-26 11:31 ` [gentoo-dev] [PATCH 3/4] kernel-install.eclass: Account for PV/KV mismatch Michał Górny
2022-10-26 11:31 ` [gentoo-dev] [PATCH 4/4] kernel-build.eclass: " Michał Górny
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=20221026113140.3213-1-mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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