On 3/8/26 12:37 PM, [email protected] wrote:
>>> 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. > > I didn't get a tree, just the usual block of packages that were supposed to > require systemd. This was the block: > > !!! All ebuilds that could satisfy "sys-apps/systemd:0/2=" have been masked. > !!! One of the following masked packages is required to complete your request: [...] > (dependency required by "sys-fs/lvm2-2.03.22-r7::gentoo" [binary]) [...] > So I tried 'emerge -1av xxx', where xxx was each of those eight. Lvm2 wanted > USE=-systemd, and the others didn't have such a USE flag. > > This is the sort of thing I meant when I said I'd been going round in circles. Odd circle to get. lvm2 "wants" USE=-systemd but nothing sets it to USE="systemd" begin with (unless you chose to do so in make.conf) Bit of a shot in the dark but did you use --binpkg-respect-use=n? That explicitly tells portage to ignore your USE flags and try installing random binpkgs with USE flags that are bad for you. Absent a terrible idea like setting this portage CLI option, there is no good reason you should ever need to manually -systemd, on an openrc profile. -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
