| 1 |
Neil, |
| 2 |
|
| 3 |
On Thursday, 2021-07-01 15:28:51 +0100, you wrote: |
| 4 |
|
| 5 |
> On Thu, 1 Jul 2021 13:16:29 +0200, Dr Rainer Woitok wrote: |
| 6 |
> |
| 7 |
> > Same here. And whenever I configure a new kernel my kernel managing |
| 8 |
> > script makes sure both, the kernel I'm currenty running on and the one |
| 9 |
> > just configured are in "@world". That way "emerge --depclean" will nev- |
| 10 |
> > er remove a kernel package. |
| 11 |
> |
| 12 |
> You can also do that with sets. Add this to sets.conf |
| 13 |
> |
| 14 |
> [kernels] |
| 15 |
> class = portage.sets.dbapi.OwnerSet |
| 16 |
> world-candidate = False |
| 17 |
> files = /usr/src |
| 18 |
> |
| 19 |
> add emerge -n @kernels once. Then depclean will never touch a kernel |
| 20 |
> source package. |
| 21 |
|
| 22 |
Nice trick, thank you :-). This would slightly simplify my kernel man- |
| 23 |
aging script. |
| 24 |
|
| 25 |
Sincerely, |
| 26 |
Rainer |
Archives