From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is it OK to get rid of app-alternatives/* ?
Date: Sun, 19 Feb 2023 10:30:41 +0000 [thread overview]
Message-ID: <20230219103041.78e1efd1@digimed.co.uk> (raw)
In-Reply-To: <Y+2skope8GnQEMfJ@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-19 10:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 1:47 [gentoo-user] Is it OK to get rid of app-alternatives/* ? Walter Dnes
2023-02-15 1:54 ` David Rosenbaum
2023-02-15 1:57 ` Michael Cook
2023-02-15 7:44 ` Walter Dnes
2023-02-15 8:11 ` Neil Bothwick
2023-02-15 14:10 ` Michael Orlitzky
2023-02-15 14:41 ` Rich Freeman
2023-02-15 15:51 ` Daniel Frey
2023-02-15 19:20 ` Wol
2023-02-15 19:48 ` Arsen Arsenović
2023-02-16 4:09 ` Walter Dnes
2023-02-19 10:30 ` Neil Bothwick [this message]
2023-03-03 0:52 ` David Rosenbaum
2023-02-15 8:53 ` Arsen Arsenović
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230219103041.78e1efd1@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox