On 08/08/2018 01:48 PM, Jeff Johnson wrote:
Adding -- and maintaining -- patterns or whitelist exceptions, which moves file dependencies into primary.xml is actually an approach that solves the problem, and scales to multiple repos as well, each of which also will have their own patterns and whitelist.
Except that it doesn't quite solve it. What happens if a third party repo package depends on a file that is not included in the Fedora whitelist? It doesn't help that the other repo has that file path in its whitelist, dnf won't be able to resolve the dependency.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/BLPPDEQL5K3VKV77DTONXX6I46HPM7YK/