Like sys-apps/systemd, sys-apps/openrc should provide (and own) /etc/modules-load.d /usr/lib/modules-load.d
For now OpenRC uses config file /etc/conf.d/modules Switching to config directory is clear and well-known trend. The only question is in it's proper path and naming. P.S. Existing config file should be moved into suggested config directory.
(In reply to Sergey S. Starikoff from comment #1) > For now OpenRC uses config file /etc/conf.d/modules https://github.com/OpenRC/openrc/commit/556dbff99d53cdcc00e6b1ec67e1679f72b6f284 But yes, modules service is still around. > The only question is in it's proper path and naming. No. This was answered and modules-load is the future. > P.S. Existing config file should be moved into suggested config directory. No. "modules" and "modules-load" service are incompatible. In "/etc/conf.d/modules" you could write specific configs per kernel version. This isn't supported in modules-load service anymore... However, topic of this bug report was owning those directories like systemd. Let's stick with the topic or please file your own bug.
In answer to the side topic of whether the "modules" service is going away, the answer is no, I do not have any plans to remove it. It actually offers more flexability than the modules-load service. The only reason for the modules-load service is to be compatible with packages that expect modules to be loaded from /usr/lib/modules-load.d and /etc/modules-load.d. I will take a look at the bugs you are linking in "see also" to find out what is going on with them.
