From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: gentoo-user@lists.gentoo.org, Neil Bothwick <neil@digimed.co.uk>
Subject: Re: [gentoo-user] system.map file in /boot. How to manage?
Date: Thu, 1 Jul 2021 17:13:41 +0200 [thread overview]
Message-ID: <24797.56229.349798.473684@tux.local> (raw)
In-Reply-To: Msg <20210701152851.44bfb79b@digimed.co.uk> of 2021-07-01 15:28:51 +0100 from neil@digimed.co.uk
Neil,
On Thursday, 2021-07-01 15:28:51 +0100, you wrote:
> On Thu, 1 Jul 2021 13:16:29 +0200, Dr Rainer Woitok wrote:
>
> > Same here. And whenever I configure a new kernel my kernel managing
> > script makes sure both, the kernel I'm currenty running on and the one
> > just configured are in "@world". That way "emerge --depclean" will nev-
> > er remove a kernel package.
>
> You can also do that with sets. Add this to sets.conf
>
> [kernels]
> class = portage.sets.dbapi.OwnerSet
> world-candidate = False
> files = /usr/src
>
> add emerge -n @kernels once. Then depclean will never touch a kernel
> source package.
Nice trick, thank you :-). This would slightly simplify my kernel man-
aging script.
Sincerely,
Rainer
next prev parent reply other threads:[~2021-07-01 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 6:59 [gentoo-user] system.map file in /boot. How to manage? Dale
2021-07-01 7:22 ` William Kenworthy
2021-07-01 11:16 ` Dr Rainer Woitok
2021-07-01 12:41 ` tastytea
2021-07-01 13:01 ` Dale
2021-07-01 14:28 ` Neil Bothwick
2021-07-01 14:41 ` Dale
2021-07-01 15:04 ` Neil Bothwick
2021-07-01 15:14 ` [gentoo-user] " Grant Edwards
2021-07-01 15:47 ` Hayley
2021-07-01 15:13 ` [gentoo-user] " antlists
2021-07-01 15:13 ` Dr Rainer Woitok [this message]
2021-07-02 23:07 ` Daniel Frey
2021-07-02 23:54 ` Dale
2021-07-03 9:11 ` J. Roeleveld
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=24797.56229.349798.473684@tux.local \
--to=rainer.woitok@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=neil@digimed.co.uk \
/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