The current Provides/Requires generation operates on a staging directory tree simulating the target deployment. This is mostly fine, except it breaks absolute symlinks within the staging directory. And, in some cases, those symlinks (and their target) participates in Provides/Requires logic. So it needs special, sometimes invasive, logic inside the generation tool.
There are probably ways to do better nowadays by making generators operate on a container overlayed oved the build root, either in rpmbuild or just when the build is orchestrated by mock.
Since overhauling this stage to make use of modern system capabilities is likely to be tricky, this is a long-term should-eventually-be-done RFE.
The current
Provides/Requiresgeneration operates on a staging directory tree simulating the target deployment. This is mostly fine, except it breaks absolute symlinks within the staging directory. And, in some cases, those symlinks (and their target) participates inProvides/Requireslogic. So it needs special, sometimes invasive, logic inside the generation tool.There are probably ways to do better nowadays by making generators operate on a container overlayed oved the build root, either in
rpmbuildor just when the build is orchestrated bymock.Since overhauling this stage to make use of modern system capabilities is likely to be tricky, this is a long-term should-eventually-be-done RFE.