This comes from bug 520404 and all the new bug reports that are constantly appearing. I refer to packages spitting this QA warning: * 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... I think we should think about not installing that files at all. For most of the packages that won't be a issue as they will create the paths when needed and, for the packages not being able to do that... they are already broken anyway as soon as, for example, user reboots and gets rid of /run dir (for example). Thanks
I think this is more of a Portage request which we'd do on EAPI bump to force people to notice, right?
This is PG 0201: https://projects.gentoo.org/qa/policy-guide/filesystem.html#pg0201 There already is a QA check metadata/install-qa-check.d/08gentoo-paths in place, which I believe is the right way to handle this. Such policies shouldn't be hardcoded, neither in PMS nor in the package manager. Reassigning to QA, and I suggest that we close this as a duplicate of bug 667604.
This bug is about installing inside these paths: /run /var/cache /var/lock /var/run (https://gitweb.gentoo.org/proj/portage.git/tree/bin/install-qa-check.d/20runtime-directories?id=9d507ee28c526662fc6ad3895a808df1814bfe01) (This file is part of Portage, so this bug needs some handling by Portage team...) PG 0201 is about installing outside different set of paths. (https://gitweb.gentoo.org/repo/gentoo.git/tree/metadata/install-qa-check.d/08gentoo-paths?id=48735f318b6509fe5bc80f9b5d2a298f9cef5d73)
If I remember well, the suggestion to change the behavior on a newer EAPI was to ensure that people will finally handle that properly with new versions... otherwise they are not fixed ever in some case and can reappear and reappear. A bit similar to the "keepdir" usage... that is now a warning... but it could be enforced in the future
