On 2026-03-08, [email protected] wrote: > Greetings, > > I've finally managed to get a more-or-less working system put together, > having > been going round in circles, banging my head on convenient walls on the way, > since before Christmas. > > I've had to abandon my favourite systemd-boot, having been unable to get it > to > work (it doesn't behave the way the handbook describes). Instead, I've had to > fall back on the dreaded grub. > > The point of this gripe, though, is that I cannot run an 'emerge -e @world' > any more, because systemd insists on being included. Well, being masked stops > it, but being explicitly excluded on the command line does not. > > Has anyone here a reliable method of ensuring that systemd stays out of the > way?
If it's installed, use emerge -pvc systemd to see what's keeping it in the dependence graph. If it's not installed, add -tv to the emerge -e options (and pipe it through a pager, or do --pretend and write to a file to look at after emerge completes the output) to get some indication of at least one of the packages that is pulling it. -- Nuno Silva
