From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] re-installed KDE doesn't start : solved
Date: Wed, 30 Jul 2025 16:58:57 +0100 [thread overview]
Message-ID: <3314135.5fSG56mABF@cube> (raw)
In-Reply-To: <13fc5bd4-a627-1ecf-7f68-2d03c85dc6a3@gmail.com>
On Wednesday, 30 July 2025 14:55:55 British Summer Time Dale wrote:
> ... I tried using sets. All it did was create
> more work. If I have something installed here, I use it, sometimes a
> LOT. Therefore, I want them all to be as up to date as is available. I
> found that even when I did have sets, the sets were in the world file
> and being updated anyway. No real point in that when just putting for
> example, kicad-meta, in the world file and skipping the sets. Some may
> like it. I've read of people using and liking how it works. For me
> tho, it was just more work. So, some of us long term users do just fine
> without sets. :-D
On the other hand, I find life easier with everything in sets. I passed through
a phase when I was reinstalling systems rather too often, and rather than sit
here for hours doing piecemeal installations, it was much easier to start a
set emerging and go and do something else while it got on with it.
I sometimes install something to see if I like it, and it goes into @world. If
I decide to keep it, it comes out of world and into a suitable set; otherwise
I uninstall it. My world file is therefore usually empty, but now you've
prompted me to check it and I see a few things in there that I thought I'd
uninstalled. So, thanks for the reminder!
Of course, now that my system is stable, more-or-less, I could revert to the
usual way of working, but then I'd have some work to do. It could be done in a
few commands; the harder part would be my having to mend my ways. :-)
In case anyone's interested, this is my standard set of sets, in order of
installation:
$ ls -1 /etc/portage/sets # arranged by hand
core
base
apps
xorg
plasma
utils
@core includes linux-firmware and gentoo-sources, which several @base packages
require to have been installed.
Many other schemes could be used, I'm sure, but mine is here for historical
reasons; not hysterical, these days :-)
--
Regards,
Peter.
next prev parent reply other threads:[~2025-07-30 16:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3720728.hdfAi7Kttb@rogueboard>
2025-07-27 10:46 ` [gentoo-user] re-installed KDE doesn't start : solved Philip Webb
2025-07-27 12:20 ` [gentoo-user] " Michael
2025-07-29 10:18 ` [gentoo-user] blocks, Blocks, shrieks Philip Webb
2025-07-29 10:42 ` Stefano Crocco
2025-07-29 10:43 ` Michael
2025-07-29 16:01 ` [gentoo-user] " Nuno Silva
2025-07-30 8:50 ` Philip Webb
2025-07-30 12:56 ` Michael
2025-07-30 15:21 ` Eli Schwartz
2025-07-31 11:28 ` [gentoo-user] " Philip Webb
2025-07-31 12:35 ` Michael
2025-07-29 20:36 ` [gentoo-user] re-installed KDE doesn't start : solved Eli Schwartz
2025-07-30 8:27 ` Philip Webb
2025-07-30 10:06 ` Michael
2025-07-30 13:55 ` Dale
2025-07-30 15:11 ` Eli Schwartz
2025-07-30 15:58 ` Peter Humphrey [this message]
2025-07-31 13:50 ` Dale
2025-08-01 13:19 ` Peter Humphrey
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=3314135.5fSG56mABF@cube \
--to=peter@prh.myzen.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