From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] adjust and note the kernel series each metapackage follows
Date: Tue, 19 Nov 2024 13:44:02 +0100 [thread overview]
Message-ID: <20241119124402.552D4239E2@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53137@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
New comment by Calandracas606 on void-packages repository
https://github.com/void-linux/void-packages/pull/53137#issuecomment-2485614994
Comment:
The way I see it, there are two situations which need solving:
1. users who need support for the latest hardware
2. users who need support for zfs and/or nvidia
IMO, problem 1 should be solved by `linux-mainline`, and problem 2 by `linux-lts`. this leaves `linux` redundant.
If keeping the `linux` package is needed, then I propose killing `linux-lts` instead, and pinning `linux` to the most recent LTS kernel supported by zfs and nvidia
Personally, I don't see the value in having a meta package for the *previous* LTS release, which will always be at least a year old. What problem is that solving? Users who really need that stability should install a specific series and stop tracking the meta.
next prev parent reply other threads:[~2024-11-19 12:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 3:35 [PR PATCH] [RFC] " classabbyamp
2024-11-19 3:54 ` [RFC] adjust and " Calandracas606
2024-11-19 4:18 ` lemmi
2024-11-19 10:35 ` leahneukirchen
2024-11-19 11:10 ` ahesford
2024-11-19 11:10 ` ahesford
2024-11-19 11:59 ` leahneukirchen
2024-11-19 12:44 ` Calandracas606 [this message]
2024-11-19 12:50 ` Calandracas606
2024-11-19 12:50 ` Calandracas606
2024-11-19 12:53 ` ahesford
2024-11-19 14:17 ` [PR PATCH] [Updated] " classabbyamp
2024-11-19 14:18 ` classabbyamp
2024-11-19 14:21 ` [PR PATCH] [Updated] " classabbyamp
2024-11-19 14:27 ` classabbyamp
2024-11-19 14:27 ` classabbyamp
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=20241119124402.552D4239E2@inbox.vuxu.org \
--to=calandracas606@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).