Dan Čermák wrote: > There is something like that already in place: > https://src.fedoraproject.org/rpms/cmake/blob/rawhide/f/cmake.req > > But I guess it does not produce the requires that you expect it should? That cmake.req script produces only dependencies on cmake-filesystem and nothing else. That is entirely unrelated to what I am talking about (though I guess the functionality I am asking for would be merged into the existing cmake.req for practical reasons). > Maybe an automatic buildrequires generator would solve your use case > better? No. These are transitive dependencies, i.e., they are not listed anywhere in the project's CMake file. There are even 2 layers of indirection, i.e., Trojitá's CMakeLists.txt requires Foo whose FooConfig.cmake requires Bar whose BarConfig.cmake requires Baz, i.e., trojita BuildRequires foo-devel which Requires bar-devel which (should) Require(s) baz-devel, and bar-devel is actually missing the Requires: baz-devel (a runtime Requires, not a BuildRequires). The only BuildRequires involved is the top-level one, and you actually need to run cmake with most build dependencies already present to see that it indirectly BuildRequires baz-devel. (There is no way a file content scan or even a cmake invocation in a minimal chroot will tell you.) So I do not see how a BuildRequires generator would help, at all. This is a missing runtime Requires from one -devel package to another, hence my request for a runtime Requires autogenerator, not a BuildRequires one. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
