[PR PATCH] [RFC] note the kernel series each metapackage follows

[PR PATCH] [RFC] note the kernel series each metapackage follows

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]

There is a new pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages linux-meta
https://github.com/void-linux/void-packages/pull/53137

[RFC] note the kernel series each metapackage follows
The current kernel metapackage policy is:

- `linux-mainline`: follows the latest available kernel
- `linux`: follows the latest available kernel that supports popular dkms modules, like `zfs` and `nvidia`
- `linux-lts`: follows an LTS release and is behind `linux`

In recent times, kernels have been released and gone EOL faster than `zfs` can release build fixes, and `nvidia` in particular has had trouble with recent kernels, holding us back from bumping `linux` to 6.10 or 6.11. In the recent past, we've had `linux` point to a kernel that was already EOL (6.3 or 6.5), so we risked not getting backports for important fixes.

I propose the following changes:

- `linux-mainline`: no change
- `linux`: follows the latest LTS release
- `linux-lts`: follows the second-latest LTS release

This should help us keep `linux` on a supported kernel and provide a more reliable indicator for when we can update the default kernel series, I think.

@void-linux/pkg-committers, thoughts?


A patch file from https://github.com/void-linux/void-packages/pull/53137.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-meta-53137.patch --]
[-- Type: text/x-diff, Size: 1975 bytes --]

From d7b85d3d4203c7626ca700b7dd7add3fc392e020 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:28 -0500
Subject: [PATCH 1/3] linux: note that it follows the latest LTS release

---
 srcpkgs/linux/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index b42a1f00cdf7fb..0b51c561d73d31 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,4 +1,5 @@
 # Template file for 'linux'
+# this package should follow the latest LTS kernel listed on kernel.org
 pkgname=linux
 version=6.6
 revision=1

From 4f47d80faf36a4881f983de7f12065dc8c87ea52 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:52 -0500
Subject: [PATCH 2/3] linux-lts: note that it follows the second-latest LTS
 release

---
 srcpkgs/linux-lts/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux-lts/template b/srcpkgs/linux-lts/template
index 638ad8aa7af01f..e9f2653b4c7683 100644
--- a/srcpkgs/linux-lts/template
+++ b/srcpkgs/linux-lts/template
@@ -1,4 +1,5 @@
 # Template file for 'linux-lts'
+# this package should follow the second-latest LTS kernel listed on kernel.org
 pkgname=linux-lts
 version=6.1
 revision=1

From 2bbbcc3d03f03cf9e6c100abd80e3df2962019ef Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:23:10 -0500
Subject: [PATCH 3/3] linux-mainline: note that it follows the latest mainline
 release

---
 srcpkgs/linux-mainline/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux-mainline/template b/srcpkgs/linux-mainline/template
index 7a07d69df76ef3..01597eec076d58 100644
--- a/srcpkgs/linux-mainline/template
+++ b/srcpkgs/linux-mainline/template
@@ -1,4 +1,5 @@
 # Template file for 'linux-mainline'
+# this package should follow the latest mainline kernel listed on kernel.org
 pkgname=linux-mainline
 version=6.11
 revision=1

Re: [RFC] adjust and note the kernel series each metapackage follows

[Calandracas606]

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

New comment by Calandracas606 on void-packages repository

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

Comment:
imo haivng `linux-lts` follow the second latest LTS release is confusing, and don't see what value it really adds.

If someone wants to use an old kernel, they probably have a good reason for it, and probably will track that specific kernel package manually 

I would propose:
`linux-mainline`: no change (eg: 6.13)
`linux`: remove
`linux-lts`: follows latest LTS with nvidia and zfs support (eg: 6.6)

Re: [RFC] adjust and note the kernel series each metapackage follows

[lemmi]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

New comment by lemmi on void-packages repository

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

Comment:
kernel.org offers `mainline`, `stable` and `longterm` versions. maybe we can try and follow that to some extent? i'd find a bit surprising for the `linux` package to track `lts` and then have another `linux-lts` package that tracks something even older.
`mainline` should more or less follow upstream, like we are doing right now.
`stable` can also follow upstream `stable`, but maybe hold a version back, in case there are known issues.
`nvidia` and `zfs` users can then depend on `linux-lts` and not hold back the other versions.

Re: [RFC] adjust and note the kernel series each metapackage follows

[leahneukirchen]

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

New comment by leahneukirchen on void-packages repository

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

Comment:
My original idea was to provide a lts package that rarely updated the major version so you don't need to fear breakage once a year.  YMMV.

Re: [RFC] adjust and note the kernel series each metapackage follows

[ahesford]

[-- 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.

Re: [RFC] adjust and note the kernel series each metapackage follows

[ahesford]

[-- Attachment #1: Type: text/plain, Size: 1077 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.

Re: [RFC] adjust and note the kernel series each metapackage follows

[leahneukirchen]

[-- Attachment #1: Type: text/plain, Size: 328 bytes --]

New comment by leahneukirchen on void-packages repository

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

Comment:
Since LTS releases appear at most annually, that sentence is redundant.  But fine by me.

This would mean we update LTS to 6.12 in February when 6.13 is mainline? (+- 1 version)

Re: [RFC] adjust and note the kernel series each metapackage follows

[Calandracas606]

[-- 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.

Re: [RFC] adjust and note the kernel series each metapackage follows

[Calandracas606]

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

New comment by Calandracas606 on void-packages repository

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

Comment:

> 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
Probably better would be to make `linux` a meta package which depends on `linux-lts`

Re: [RFC] adjust and note the kernel series each metapackage follows

[Calandracas606]

[-- Attachment #1: Type: text/plain, Size: 406 bytes --]

New comment by Calandracas606 on void-packages repository

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

Comment:
> 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

Probably better would be to make `linux` a meta package which depends on `linux-lts`

Re: [RFC] adjust and note the kernel series each metapackage follows

[ahesford]

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

New comment by ahesford on void-packages repository

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

Comment:
I don't know that either meta package is *needed*, but removing one is going to break workflows for people who use them to track new releases. Dropping -lts is probably the least surprising.

Re: [PR PATCH] [Updated] [RFC] adjust and note the kernel series each metapackage follows

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages linux-meta
https://github.com/void-linux/void-packages/pull/53137

[RFC] adjust and note the kernel series each metapackage follows
The current kernel metapackage policy is:

- `linux-mainline`: follows the latest available kernel
- `linux`: follows the latest available kernel that supports popular dkms modules, like `zfs` and `nvidia`
- `linux-lts`: follows an LTS release and is behind `linux`

In recent times, kernels have been released and gone EOL faster than `zfs` can release build fixes, and `nvidia` in particular has had trouble with recent kernels, holding us back from bumping `linux` to 6.10 or 6.11. In the recent past, we've had `linux` point to a kernel that was already EOL (6.3 or 6.5), so we risked not getting backports for important fixes.

I propose the following changes:

- `linux-mainline`: no change
- `linux`: follows the latest LTS release
- `linux-lts`: follows the second-latest LTS release

This should help us keep `linux` on a supported kernel and provide a more reliable indicator for when we can update the default kernel series, I think.

@void-linux/pkg-committers, thoughts?


A patch file from https://github.com/void-linux/void-packages/pull/53137.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-meta-53137.patch --]
[-- Type: text/x-diff, Size: 4250 bytes --]

From d7b85d3d4203c7626ca700b7dd7add3fc392e020 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:28 -0500
Subject: [PATCH 1/5] linux: note that it follows the latest LTS release

---
 srcpkgs/linux/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index b42a1f00cdf7fb..0b51c561d73d31 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,4 +1,5 @@
 # Template file for 'linux'
+# this package should follow the latest LTS kernel listed on kernel.org
 pkgname=linux
 version=6.6
 revision=1

From 4f47d80faf36a4881f983de7f12065dc8c87ea52 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:52 -0500
Subject: [PATCH 2/5] linux-lts: note that it follows the second-latest LTS
 release

---
 srcpkgs/linux-lts/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux-lts/template b/srcpkgs/linux-lts/template
index 638ad8aa7af01f..e9f2653b4c7683 100644
--- a/srcpkgs/linux-lts/template
+++ b/srcpkgs/linux-lts/template
@@ -1,4 +1,5 @@
 # Template file for 'linux-lts'
+# this package should follow the second-latest LTS kernel listed on kernel.org
 pkgname=linux-lts
 version=6.1
 revision=1

From 2bbbcc3d03f03cf9e6c100abd80e3df2962019ef Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:23:10 -0500
Subject: [PATCH 3/5] linux-mainline: note that it follows the latest mainline
 release

---
 srcpkgs/linux-mainline/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux-mainline/template b/srcpkgs/linux-mainline/template
index 7a07d69df76ef3..01597eec076d58 100644
--- a/srcpkgs/linux-mainline/template
+++ b/srcpkgs/linux-mainline/template
@@ -1,4 +1,5 @@
 # Template file for 'linux-mainline'
+# this package should follow the latest mainline kernel listed on kernel.org
 pkgname=linux-mainline
 version=6.11
 revision=1

From 67b6541d8449db60c39d61e83ff04a9a16d28811 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 19 Nov 2024 09:15:54 -0500
Subject: [PATCH 4/5] fixup! linux: note that it follows the latest LTS release

---
 srcpkgs/linux/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index 0b51c561d73d31..ae65e76100f0e7 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,5 +1,6 @@
 # Template file for 'linux'
-# this package should follow the latest LTS kernel listed on kernel.org
+# this package should follow the latest supported kernel
+# that supports common dkms modules like nvidia and zfs
 pkgname=linux
 version=6.6
 revision=1

From 8e17977696ca2e172a1d32d8436028d83f94982c Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 19 Nov 2024 09:16:32 -0500
Subject: [PATCH 5/5] New package: linux-stable-6.11

tracks what kernel.org calls stable (generally 1 release behind mainline)
---
 srcpkgs/linux-stable/template | 16 ++++++++++++++++
 srcpkgs/linux-stable/update   |  2 ++
 2 files changed, 18 insertions(+)
 create mode 100644 srcpkgs/linux-stable/template
 create mode 100644 srcpkgs/linux-stable/update

diff --git a/srcpkgs/linux-stable/template b/srcpkgs/linux-stable/template
new file mode 100644
index 00000000000000..fa27207809b722
--- /dev/null
+++ b/srcpkgs/linux-stable/template
@@ -0,0 +1,16 @@
+# Template file for 'linux-stable'
+# this package should follow the latest stable kernel listed on kernel.org
+pkgname=linux-stable
+version=6.11
+revision=1
+build_style=meta
+depends="linux${version} linux-base"
+short_desc="Linux latest stable kernel meta package"
+maintainer="Leah Neukirchen <leah@vuxu.org>"
+license="Public Domain"
+homepage="http://www.voidlinux.org/"
+
+linux-mainline-headers_package() {
+	short_desc="Linux latest stable kernel headers meta package"
+	depends="linux${version}-headers"
+}
diff --git a/srcpkgs/linux-stable/update b/srcpkgs/linux-stable/update
new file mode 100644
index 00000000000000..884fa30db8edbd
--- /dev/null
+++ b/srcpkgs/linux-stable/update
@@ -0,0 +1,2 @@
+site="https://www.kernel.org/feeds/kdist.xml"
+pattern="<title>\K\d+.\d+(?=: mainline</title>)"

Re: [RFC] adjust and note the kernel series each metapackage follows

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 434 bytes --]

New comment by classabbyamp on void-packages repository

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

Comment:
based on discussion on IRC, I've added `linux-stable`, a package that follows what kernel.org calls stable, and adjusted the description of `linux`.

In the long term, it would be nice to make `linux` into a virtual package, which would allow for more flexible kernel series switching.

Re: [PR PATCH] [Updated] [RFC] adjust and note the kernel series each metapackage follows

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages linux-meta
https://github.com/void-linux/void-packages/pull/53137

[RFC] adjust and note the kernel series each metapackage follows
The current kernel metapackage policy is:

- `linux-mainline`: follows the latest available kernel
- `linux`: follows the latest available kernel that supports popular dkms modules, like `zfs` and `nvidia`
- `linux-lts`: follows an LTS release and is behind `linux`

In recent times, kernels have been released and gone EOL faster than `zfs` can release build fixes, and `nvidia` in particular has had trouble with recent kernels, holding us back from bumping `linux` to 6.10 or 6.11. In the recent past, we've had `linux` point to a kernel that was already EOL (6.3 or 6.5), so we risked not getting backports for important fixes.

I propose the following changes:

- `linux-mainline`: no change
- `linux`: follows the latest LTS release
- `linux-lts`: follows the second-latest LTS release

This should help us keep `linux` on a supported kernel and provide a more reliable indicator for when we can update the default kernel series, I think.

@void-linux/pkg-committers, thoughts?


A patch file from https://github.com/void-linux/void-packages/pull/53137.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-meta-53137.patch --]
[-- Type: text/x-diff, Size: 4569 bytes --]

From d7b85d3d4203c7626ca700b7dd7add3fc392e020 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:28 -0500
Subject: [PATCH 1/5] linux: note that it follows the latest LTS release

---
 srcpkgs/linux/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index b42a1f00cdf7fb..0b51c561d73d31 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,4 +1,5 @@
 # Template file for 'linux'
+# this package should follow the latest LTS kernel listed on kernel.org
 pkgname=linux
 version=6.6
 revision=1

From 4f47d80faf36a4881f983de7f12065dc8c87ea52 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:52 -0500
Subject: [PATCH 2/5] linux-lts: note that it follows the second-latest LTS
 release

---
 srcpkgs/linux-lts/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux-lts/template b/srcpkgs/linux-lts/template
index 638ad8aa7af01f..e9f2653b4c7683 100644
--- a/srcpkgs/linux-lts/template
+++ b/srcpkgs/linux-lts/template
@@ -1,4 +1,5 @@
 # Template file for 'linux-lts'
+# this package should follow the second-latest LTS kernel listed on kernel.org
 pkgname=linux-lts
 version=6.1
 revision=1

From 2bbbcc3d03f03cf9e6c100abd80e3df2962019ef Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:23:10 -0500
Subject: [PATCH 3/5] linux-mainline: note that it follows the latest mainline
 release

---
 srcpkgs/linux-mainline/template | 1 +
 1 file changed, 1 insertion(+)

diff --git a/srcpkgs/linux-mainline/template b/srcpkgs/linux-mainline/template
index 7a07d69df76ef3..01597eec076d58 100644
--- a/srcpkgs/linux-mainline/template
+++ b/srcpkgs/linux-mainline/template
@@ -1,4 +1,5 @@
 # Template file for 'linux-mainline'
+# this package should follow the latest mainline kernel listed on kernel.org
 pkgname=linux-mainline
 version=6.11
 revision=1

From 67b6541d8449db60c39d61e83ff04a9a16d28811 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 19 Nov 2024 09:15:54 -0500
Subject: [PATCH 4/5] fixup! linux: note that it follows the latest LTS release

---
 srcpkgs/linux/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index 0b51c561d73d31..ae65e76100f0e7 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,5 +1,6 @@
 # Template file for 'linux'
-# this package should follow the latest LTS kernel listed on kernel.org
+# this package should follow the latest supported kernel
+# that supports common dkms modules like nvidia and zfs
 pkgname=linux
 version=6.6
 revision=1

From acba1d9b3a868f6c40375fa485c045c00a58ce73 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 19 Nov 2024 09:16:32 -0500
Subject: [PATCH 5/5] New package: linux-stable-6.11

tracks what kernel.org calls stable (generally 1 release behind mainline)
---
 srcpkgs/linux-stable-headers  |  1 +
 srcpkgs/linux-stable/template | 16 ++++++++++++++++
 srcpkgs/linux-stable/update   |  2 ++
 3 files changed, 19 insertions(+)
 create mode 120000 srcpkgs/linux-stable-headers
 create mode 100644 srcpkgs/linux-stable/template
 create mode 100644 srcpkgs/linux-stable/update

diff --git a/srcpkgs/linux-stable-headers b/srcpkgs/linux-stable-headers
new file mode 120000
index 00000000000000..20b12c956783e6
--- /dev/null
+++ b/srcpkgs/linux-stable-headers
@@ -0,0 +1 @@
+linux-stable
\ No newline at end of file
diff --git a/srcpkgs/linux-stable/template b/srcpkgs/linux-stable/template
new file mode 100644
index 00000000000000..b8d3402315a14b
--- /dev/null
+++ b/srcpkgs/linux-stable/template
@@ -0,0 +1,16 @@
+# Template file for 'linux-stable'
+# this package should follow the latest stable kernel listed on kernel.org
+pkgname=linux-stable
+version=6.11
+revision=1
+build_style=meta
+depends="linux${version} linux-base"
+short_desc="Linux latest stable kernel meta package"
+maintainer="Leah Neukirchen <leah@vuxu.org>"
+license="Public Domain"
+homepage="http://www.voidlinux.org/"
+
+linux-stable-headers_package() {
+	short_desc="Linux latest stable kernel headers meta package"
+	depends="linux${version}-headers"
+}
diff --git a/srcpkgs/linux-stable/update b/srcpkgs/linux-stable/update
new file mode 100644
index 00000000000000..b51c37be09587b
--- /dev/null
+++ b/srcpkgs/linux-stable/update
@@ -0,0 +1,2 @@
+site="https://www.kernel.org/feeds/kdist.xml"
+pattern="<title>\K\d+.\d+(?=: stable</title>)"

Re: [RFC] adjust and note the kernel series each metapackage follows

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 375 bytes --]

New comment by classabbyamp on void-packages repository

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

Comment:
also, I started trying to make `linux-headers` a virtual, and it didn't work while `linux`/`linux-headers` existed as a real package (and maybe another issue, i forget now): https://github.com/void-linux/void-packages/pull/43519

Re: [RFC] adjust and note the kernel series each metapackage follows

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 426 bytes --]

New comment by classabbyamp on void-packages repository

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

Comment:
also, I started trying to make `linux-headers` a virtual, and it didn't work while `linux`/`linux-headers` existed as a real package (and maybe another issue, i forget now): https://github.com/void-linux/void-packages/pull/43519

so there are maybe things that this would solve