| View previous topic :: View next topic |
| Author |
Message |
mf2
n00b
Joined: 14 Jun 2007
Posts: 48
|
 Posted: Mon Sep 23, 2024 6:09 am Post subject: Can you keep the oldest stable version of a slotted pkg? |
 |
|
So I am using gentoo-sources as a kernel on my system, which is fine. However, updates to the kernel come to fast for my taste. Since the package offers various slots, is it possible to tell emerge somehow to keep it on the oldest slot and to only upgrade it if that slot is being removed?
Example: Let's say I am on gentoo-sources-5.10.224. When that slot leaves the portage tree, on a world update I want it to go to 5.10.226, not 6.11.0. Can this be achieved?
Of course I could mask the newer versions and lift the masks gradually, but I fear that I will miss updates then and stay on a deprecated kernel for too long. |
|
| Back to top |
|
 |
sam_
Developer
Joined: 14 Aug 2020
Posts: 1962
|
| Posted: Mon Sep 23, 2024 6:44 am Post subject: |
|
|
Most (not all) of what you want here is to pin to a particular release series. We tried changing the slots in gentoo-sources a little while ago but people didn't like that. At some point I plan to propose something like a virtual for specific series (at least LTS) which pins to each one so people can emerge that and get that behaviour (or something along those lines).
For now, you can do something like this in package.mask:
sys-kernel/gentoo-sources
Then in package.unmask:
=sys-kernel/gentoo-sources-5.10* |
|
| Back to top |
|
|
mf2
n00b
Joined: 14 Jun 2007
Posts: 48
|
| Posted: Mon Sep 23, 2024 8:38 am Post subject: |
|
|
| Thank you! |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3425
Location: Canada
|
| Posted: Mon Sep 23, 2024 4:29 pm Post subject: |
|
|
| sam_ wrote: | Most (not all) of what you want here is to pin to a particular release series. We tried changing the slots in gentoo-sources a little while ago but people didn't like that. At some point I plan to propose something like a virtual for specific series (at least LTS) which pins to each one so people can emerge that and get that behaviour (or something along those lines).
For now, you can do something like this in package.mask:
sys-kernel/gentoo-sources
Then in package.unmask:
=sys-kernel/gentoo-sources-5.10* |
I guess you can simply mask
>=sys-kernel/gentoo-sources-5.11.0
to remain on 5.10 and its updates without dealing with unmask file
I myself usually change the kernels until all the hardware on my new machine works. At that point I often upgrade my older machines to match versions. And then freeze it for a long time until I buy I new hardware or some
dramatic development happens. Was on 4.19 from 2018 until this January, when I moved to 5.15. Currently got a new but not yet set up laptop, and am waiting for 6.10 to become stable. Expect several updates until freeze to some LTE version. |
|
| Back to top |
|
|
|
Portage & Programming
