Neil Bothwick wrote: > On Mon, 4 Oct 2021 21:31:35 +0200, Arve Barsnes wrote: > >>> On Mon, 4 Oct 2021 10:33:58 +0200, Arve Barsnes wrote: >>> I picked up this tip some years ago to avoid depcleaning kernel >>> sources. >>> >>> % cat /etc/portage/sets.conf >>> [kernels] >>> class = portage.sets.dbapi.OwnerSet >>> world-candidate = False >>> files = /usr/src >>> >>> and emerge -n @kernels >> Interesting way to do it. I want them depcleaned though, as soon as I >> confirm that the new kernel works as expected. I use a custom >> patch-set, so I never have any updates unless I add them myself, so >> I'm not sure if using a set would give me anything. > Fair enough. I use standard gentoo-sources but always like to keep at > least one previous version available "just in case". I unmerge old > versions manually, I have to delete kernel sources manually anyway as > emerge only removes the files it installed, leaving all the files created > when compiling the kernel. > >
I "borrowed" your method a good while back and do it the same way. Even if I use emerge to remove it, it always leaves cruft behind so I just do it manually then tell emerge to remove it from its info. I sometimes end up with 3 to 4 kernels. Before the init thingys came along, I didn't worry about removing kernels. I just left them since space wasn't a issue. With the init thingys tho, it doubles or so the space needed for each kernel. So, when I get a couple new stable ones, I delete old ones to keep a little breathing room. Your way is nifty. No more editing package files every time I want to upgrade or something. Dale :-) :-)
