From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Using virtualpkg to pin a kernel version
Date: Sat, 04 Sep 2021 22:32:32 +0200 [thread overview]
Message-ID: <20210904203232.jr287dvkY7PvDbHqRLotsvMjDEiOXsOXMKJssc9qkFk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32833@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/32833#issuecomment-913036791
Comment:
> My current plan with linux-base was to document removing `linux` and marking it manual, then choosing your preferred version for the kernel. There's an open issue about it in the void-docs repo. Do you think that's too error prone?
Not too error prone, but if I'm not missing anything the way I propose is one step less.
1. current solution
- `ignorepkg=linux`
- mark `linux-base` manual
- remove `linux`
- install `linux5.10`
2. my proposal
-`ignorepkg=linux-kernel`
- remove `linux-kernel`
- install `linux5.10`
Not a big difference. Better imo would be if `virtualpkg=linux-kernel:linux5.10` followed by `xi -u` would be all that's needed.
next prev parent reply other threads:[~2021-09-04 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 16:30 [ISSUE] " tornaria
2021-09-04 20:13 ` ericonr
2021-09-04 20:27 ` tornaria
2021-09-04 20:32 ` Chocimier
2021-09-04 20:32 ` tornaria [this message]
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=20210904203232.jr287dvkY7PvDbHqRLotsvMjDEiOXsOXMKJssc9qkFk@z \
--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).