profile 23 - ignored packages non matching use

[hunky]

Going thru the steps on what was a 17.1 amd64 desktop plasma non-systemd system and got to the emerge world empty tree command and I get a bunch of ignored packages (lots have systemd USE which I hope to avoid where I can). I have gone thru my package.use file to make sure I don't have duplicates of any of these files in there (been using gentoo a long time).

Should I proceed regardless these ignored packages or is there something I should do to fix it? I haven't a clue why some of these are duplicated - some more than once.

[logrusx]

That means those packages will be compiled because their use flags do not match the flags with which the binary packages were built. You can either continue and build them or adjust the use flags wherever you consider it OK for you and maximize the list of binary packages that will be used.

In the list it's shown what change need to be made, e.g. -abi_x86_32 means you need to turn off the 32bit support for those packages as you can't get it from binary packages. If the case is like mine where those are needed by wine you have no choice but rebuild them.

Furthermore it looks like this is an OpenRC installation and it doesn't make sense for you to enable systemd support to accommodate the packages required to have it for the binary package to be used. However systemd support alone doesn't do much, so it could be a viable option even for OpenRC users who just want to use binary packages. This route should be further explored if someone is interested as it's beyond me.

Best Regards,
Georgi

[e8root]

My understanding is that there are multiple version of binary packages which have been built by Gentoo binary package build system and each duplicated entry here present possible option for you what changes to make to be able to use binary package. Having to build each package in multiple versions is a much bigger burden than binary packages in most distros. Ideally we would have each permutation of each package for each CPU type but this is not feasible... unless some millionaire Gentoo enthusiast funds such endeavor

Out of interest what is available in regards to systemd vs -systemd I checked each systemd entry and it seems almost all systemd entries have the same option without systemd specific use flags.

Why this entry =sys-apps/systemd-utils-254.8 -abi_x86_32 -split-usr?
It is probably something installed as a dependency for some package which has systemd related use flag - if this is not systemd system then you should probably check your packages and adjust accordingly so such systemd packages are not installed.

ps.

[flexibeast]

[logrusx]

[hunky]

[Hu]

To get the full benefit of the profile changes, you need all your native programs rebuilt with the new toolchain settings. emerge --emptytree @world ensures that happens. Using emerge --emptytree --getbinpkg @world is offered as an alternative for people who want the new settings, but do not want to spend time rebuilding @world. That command will reinstall everything, and use binary packages built by the Gentoo project wherever it can. Going forward, you can do your regular system updates without --getbinpkg, and the system will slowly adjust back to being built exactly as you like it. Alternatively, if you have the CPU cycles to spare and want maximal control, you can omit --getbinpkg and do all the rebuilds locally.

You also have the option of not rebuilding everything right now, and letting that get picked up over time. However, absent specific encouragement from the Gentoo developers to do that, I cannot recommend it, as I have no insight into whether this will make your system too different from baseline for us to help you. I am not aware of anything that will break, but we do know that you will not get the benefits of the improved toolchain until you install binaries built with it, either built for you (--getbinpkg) or built locally (without --getbinpkg).

[hunky]

[logrusx]

[hunky]