On 29. 03. 21 0:11, Otto Urpelainen wrote:
Miro Hrončok kirjoitti 28.3.2021 klo 23.23:
>> On Sun, Mar 28, 2021 at 2:48 PM Miro Hrončok <mhroncok(a)redhat.com>
>> Weird, I was under the impression that to fix the "unowned directory
>> problem" you had to "just" add "Requires:
>> package shipping the icons.
> That is correct.
>> All my GUI application packages that ship
>> their own icons do that. Why would that dependency not be necessary?
> I think we are misunderstanding each other here.
So the correct method is "Requires: hicolor-icon-theme". The reason I initially
understood this differently was this:
1. the guidelines give _filesystem_ and "other explicitly created filesystem
packages" the same standing in this phrase: "any directories owned by the
filesystem, man, or other explicitly created -filesystem packages"
2. _filesystem_ is not given special treatment anywhere
3. you do not do "Requires: filesystem" to get /usr/bin created
Which sounds like a contrived argument, but really I really was just trying to
figure out how it should be done.
I already opened a pull request to clarify this, I have to redo it.
OK, I now see where I made this more confusing.
Let me clarify:
1) hicolor-icon-theme "acts" like a filesystem package
2) except you need to Require it
Many other packages work like this (e.g. python-jupyter-filesystem, python3-jaraco).
Random idea: Let's have a database of those and generate the requirement on them