Thanks Dave
On Sun, Feb 19, 2023, 05:31 Neil Bothwick <[email protected]> wrote: > On Wed, 15 Feb 2023 23:09:54 -0500, Walter Dnes wrote: > > > > It's bad enough depclean deleting the active kernel if you don't > > > watch out, without something deciding to install a non-existent > > > kernel and deleting the live one :-) > > > > I have my own hand-coded script that runs "emerge --pretend > > --depclean" and tweaks/filters the output into another script called > > "cleanscript". I've set it to filter out "gentoo-sources". I then > > inspect "cleanscript" before running it. And, oh yeah, depclean wants > > to remove nano. I had to "emerge -n nano" to protect it. > > You can add kernel sources to a set so they are never depcleaned > > % cat sets.conf > [kernels] > class = portage.sets.dbapi.OwnerSet > world-candidate = False > files = /usr/src > > Then emerge -n @kernels > > I do the same with gcc so I can keep the previous version > > [gcc] > class = portage.sets.dbapi.OwnerSet > world-candidate = False > files = /usr/x86_64-pc-linux-gnu/gcc-bin > > > -- > Neil Bothwick > > For security reasons, all text in this mail > is double-rot13 encrypted. >
