On 4/26/19 9:32 AM, Michał Górny wrote: > > Whether it can be deleted is up to system's configuration. The current > solution works for majority of cases, including a. people who use > systemd or OpenRC, and set their systems to clean it up, and b. people > who don't use either but don't clean it up. > > We can't support everyone, and a small potential minority for whose this > might not work is no excuse to replace it with a worse solution. >
https://www.youtube.com/watch?v=yjfrJzdx7DA I don't believe that one of the world's foremost experts on package management is stumped trying to configure a common cache directory. But, I've let you change the subject. We're only talking about eix because you gave it as an example of a package that needs the RDEPEND=virtual/tmpfiles in the eclass, claiming that it needs tmpfiles_process() to work. Yet you've acknowledged that this is an eix-specific hack that won't work in some cases. In cases like that, adding RDEPEND=virtual/tmpfiles to the ebuild is a better solution, because (a) the end result is exactly the same, (b) it keeps the dependency out of the eclass, and (c) it localizes the dependency to the place that needs it, namely the wacky package. In cases like that, using a simple "dodir /var/cache/eix" is a better solution because (a) the end result is exactly the same, (b) it keeps the dependency out of the eclass, and (c) doesn't need a dependency on virtual/tmpfiles at all. Both are preferable in the case of app-portage/eix, so I don't buy it as justification for keeping the RDEPEND in the eclass. Are there better examples?
