This is an auto-filled bug because this package should create some paths at runtime. * QA Notice: This ebuild installs into paths that should be created at runtime. * To fix, simply do not install into these directories. Instead, your package * should create dirs on the fly at runtime as needed via init scripts/etc... * * var/run * var/run/brltty
I have entries for those paths in /usr/lib/tmpfiles.d, which is what I thought we were supposed to do. In that case, isn't creating those dirs at install time completely harmless? They'll be blown away at reboot / shutdown and then recreated by the scripts that make tempfiles, right? I mean, I could run rm in the ebuild. If I do that, the directories won't be available for the daemon if someone decides to start it before the next boot. So I could add code to my initscript to create the directory before the daemon starts. Fine. Now my tmpfiles.d entry is completely superfluous. May as well remove it, eh? Sounds like I've just made more work for myself, adding code to both an ebuild and an initscript, while losing the convenience of tmpfiles.d. Sorry if my tone is a bit hostile. But I think what I have here is just fine. If not, please give me a good contrary argument. Thanks.
Well, as it turns out, brltty will create the paths at runtime if they're missing. So I'll add some rmdirs to the ebuilds and problem solved.
Fixed in 5.1. It's a false positive in 5.0.
