From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [RFC] Using virtualpkg to pin a kernel version
Date: Sat, 04 Sep 2021 18:30:37 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32833@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
New issue by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833
Description:
Suppose I want to pin my kernel to 5.10, which is the latest LTS.
I can configure
```
virtualpkg=linux:linux5.10
virtualpkg=linux-headers:linux5.10-headers
```
in xbps.d. This works fine in the sense that `linux5.10` will be installed instead of `linux5.13` and it is future proof (contrary to `virtualpkg=linux5.13:linux5.10` which will break when kernel is switched to 5.14).
However, this results in the `linux-base` package as orphan. Of course, I can just change `linux-base` to manual and be done with it, but if I forget this could lead to a broken system and it is more steps to document (and since this is not documented, I don't know if something will change in the future that breaks my system).
I wonder if it would make sense to have a different meta package, say `linux-kernel`, whose only purpose is to depend on `linux${version}`, just like `linux-headers` only purpose is to depend on `linux${version}-headers`.
Then `linux` would be a meta package that depends on `linux-kernel` and `linux-base` (or the actual dependencies as linux-base might become superfluous), and linux kernel version can be pinned easily with virtualpkgs as above. This seems robust enough to be documented in the manual, etc.
---
In fact, it seems the current `linux-base` pkg could just be renamed `linux` adding `linux-kernel` dependency, and the current `linux` could just be renamed `linux-kernel`, keeping `linux-headers` as a subpkg of `linux-kernel`.
next reply other threads:[~2021-09-04 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 16:30 tornaria [this message]
2021-09-04 20:13 ` ericonr
2021-09-04 20:27 ` tornaria
2021-09-04 20:32 ` Chocimier
2021-09-04 20:32 ` tornaria
2021-09-04 20:32 ` tornaria
2021-09-04 20:36 ` tornaria
2022-06-05 2:14 ` github-actions
2022-06-19 2:15 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32833@inbox.vuxu.org \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).