Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@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 12:10:28 +0100	[thread overview]
Message-ID: <20241119111028.97B902FDCD@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: 1078 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/53137#issuecomment-2485413880

Comment:
> `nvidia` and `zfs` users can then depend on `linux-lts` and not hold back the other versions.

I take pride that our ZFS support is best in class. Shipping a `linux` package that frequently fails to work with ZFS---especially when it is the default kernel for the distribution---is not acceptable. Likewise, a default kernel package that can't provide video to large numbers of users is no good.

As there is momentum behind keeping the `linux` package the distribution default, we can't change that now. We are *de facto* pinning `linux` at the latest LTS kernel, so let's codify that. In keeping with the spirit of @leahneukirchen's intention with `linux-lts`, we could amend the proposal slightly:
`linux-lts` can point to a prior LTS kernel such that it is never the same series as `linux` and is updated at most annually. Users looking for longer stability should just install a specific series and stop tracking the metas.

  parent reply	other threads:[~2024-11-19 11:10 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 [this message]
2024-11-19 11:10 ` ahesford
2024-11-19 11:59 ` leahneukirchen
2024-11-19 12:44 ` Calandracas606
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=20241119111028.97B902FDCD@inbox.vuxu.org \
    --to=ahesford@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).