Matthew Miller wrote:
> But that's policy as well. It would be reasonable to have a different
> policy, like "build and soft dependencies are okay from base -> secondary,
> but not hard runtime requirements".
But a build-time dependency often automatically results in a hard runtime
dependency, e.g., for C/C++ libraries.
A common issue in the Core vs. Extras days was that a package in Core had to
be compiled without some compile-time-optional feature because that feature
would have depended on a library in Extras. The above proposal would not
solve this issue.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
