Description of problem:
I noticed that when building packages requiring doxygen in mock locally or via COPR, that libaom, rav1e-libs, svt-av1-libs, and libdav1d were installed.
I first noticed this when COPR builds for aom would fail because it could not find the corresponding libaom (the corresponding libaom would have been built during the build of the aom package).
In an effort to determine the problem, I noticed I could build aom if I disabled documentation, and therefore requiring doxygen.
I also noticed that if I initialise mock and install doxygen, the above libs are installed. Procedure:
mock --install dnf
mock --shell bash
dnf install doxygen (within mock, of course)
The above also happens with mock -r fedora-34-x86_64
Am I missing something?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
After some investigation it seems that the "chain" installation dependencies is like this:
doxygen -> graphviz -> gd -> libavif -> (libaom + libdav1d + svt-av1-libs)
This seems to make no sense, because to build libaom or libdav1d, doxygen is required.
These install dependencies occur inside or outside of mock.
Am I misunderstanding something?