* [ISSUE] [RFC] kernel-libc-headers policy
@ 2021-10-24 16:02 ericonr
2021-11-02 12:18 ` q66
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: ericonr @ 2021-10-24 16:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33729
Description:
We currently keep kernel-libc-headers stuck to the latest LTS kernel release. Is there any reason we can't update it for each kernel release, besides the time it takes to build cross toolchains?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [RFC] kernel-libc-headers policy
2021-10-24 16:02 [ISSUE] [RFC] kernel-libc-headers policy ericonr
@ 2021-11-02 12:18 ` q66
2021-11-04 1:07 ` ericonr
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: q66 @ 2021-11-02 12:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 160 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33729#issuecomment-957428044
Comment:
why would we do that?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [RFC] kernel-libc-headers policy
2021-10-24 16:02 [ISSUE] [RFC] kernel-libc-headers policy ericonr
2021-11-02 12:18 ` q66
@ 2021-11-04 1:07 ` ericonr
2021-11-04 12:34 ` q66
2021-11-14 1:41 ` [ISSUE] [CLOSED] " ericonr
3 siblings, 0 replies; 5+ messages in thread
From: ericonr @ 2021-11-04 1:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33729#issuecomment-960352180
Comment:
So users and programs can take advantage of advancements in `linux` more easily, like the addition of landlock and such.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [RFC] kernel-libc-headers policy
2021-10-24 16:02 [ISSUE] [RFC] kernel-libc-headers policy ericonr
2021-11-02 12:18 ` q66
2021-11-04 1:07 ` ericonr
@ 2021-11-04 12:34 ` q66
2021-11-14 1:41 ` [ISSUE] [CLOSED] " ericonr
3 siblings, 0 replies; 5+ messages in thread
From: q66 @ 2021-11-04 12:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33729#issuecomment-960816787
Comment:
in that case, worry about updating musl first
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ISSUE] [CLOSED] [RFC] kernel-libc-headers policy
2021-10-24 16:02 [ISSUE] [RFC] kernel-libc-headers policy ericonr
` (2 preceding siblings ...)
2021-11-04 12:34 ` q66
@ 2021-11-14 1:41 ` ericonr
3 siblings, 0 replies; 5+ messages in thread
From: ericonr @ 2021-11-14 1:41 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
Closed issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33729
Description:
We currently keep kernel-libc-headers stuck to the latest LTS kernel release. Is there any reason we can't update it for each kernel release, besides the time it takes to build cross toolchains?
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-11-14 1:41 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-24 16:02 [ISSUE] [RFC] kernel-libc-headers policy ericonr
2021-11-02 12:18 ` q66
2021-11-04 1:07 ` ericonr
2021-11-04 12:34 ` q66
2021-11-14 1:41 ` [ISSUE] [CLOSED] " ericonr
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).