On my setup (profile default/linux/amd64/23.0/split-usr/hardened/selinux, OpenRC 0.54.2) the plymouth.so from the emerged package is placed in the /usr/lib64/rc/plugins folder. This is not then picked up by OpenRC. Manually adding a symlink /lib64/rc -> /usr/lib64/rc fixes the issue, as does downgrading to v0.1.3, which installs the so file in the /lib64/rc/plugins directory. Likely a bad interaction with the split-usr profile.
Thanks for the bug report, that's a great pointer. I replaced the build system in 0.2.0, it should be pretty straightforward to resolve. Once I'm done with chromium I'll take a look.
A commit has been merged in OpenRC that enables the generation of pkgconfig files that include the appropriate path for module installation. We'll need to wait for a new OpenRC release to fix this "properly" but I'll try and get a patch out shortly that should be better than the current behaviour.
This should "just work" for the new 0.3.0 release and onwards. It does require accepting the testing keyword for the 0.55 release of OpenRC because that's where we now source the 'where do I install my plugin' info. Let me know how it goes when you have a chance to try it out. Thanks!
Hi, Thanks for the fix. Just updated OpenRC to 0.55 and the plymouth plugin to 0.3.0. The file ended up in /lib/rc/plugins (as per the pkg-config definitions) and is still not picked up by OpenRC. Symlinking /lib/rc -> /lib64/rc again fixes the issue. This may be more of a configuration issue (on the OpenRC side) at this point. When emerging the new OpenRC I get the following notice: * QA Notice: pkg-config files not respecting libdir found * (contains reference to either lib or lib64 in wrong directory) * /usr/lib64/pkgconfig/openrc.pc I don't have the time to dig into it right now, but if you need anything more to go on then feel free let me know.
(In reply to Matt Jolly from comment #3) > This should "just work" for the new 0.3.0 release and onwards. It does > require accepting the testing keyword for the 0.55 release of OpenRC because > that's where we now source the 'where do I install my plugin' info. > > Let me know how it goes when you have a chance to try it out. Thanks! Still doesn't work with openrc-0.55 because plymouth-openrc-plugin-0.3.0 now install plymouth.so in /lib/rc/plugins OpenRC expect to find this file in /lib64/rc/plugins Moving /lib/rc/plugins directory to /lib64/rc/ "fix" the issue for me.
> Likely a bad interaction with the split-usr profile. No, this is also broken on merged-usr profiles. I’m using default/linux/amd64/23.0/hardened This is more likely related to amd64/multilib profiles, because /lib/rc is still symlinked to /usr/lib/rc on these profiles instead of /usr/lib64 where openrc appears to look for plugins. So the fix would be to set #/usr/lib64/pkgconfig/openrc.pc ... rc_path=/lib64/rc ...
To paraphase some discussion in IRC. ``` #define RC_PLUGINDIR RC_LIBDIR "/plugins" -> #define RC_LIBDIR "/lib64/rc" ``` We failed to catch this when implementing the pkgconfig stuff upstream. The current plan is to evaluate moving plugins to `/usr/libexec/openrc/plugins` and libdir to `/lib/openrc`. We'll see what happens and I'll push a fix as soon as we have something (or an interim solution if it's not looking like a quick fix). CC Anna to track this issue. In the immediate short term symlinking the file to /lib64/ is a perfectly cromulent solution.
