On 2019-03-26 10:07 a.m., Georg Sauthoff wrote:
Hello,
when packaging a C/C++ program, the rpm automatic dependency feature
usually works well for shared libraries.
That mean when program 'bar' needs libfoo-devel at build time it's
sufficient to add
BuildRequires: libfoo-devel
and I can omit
Requires: libfoo
because rpm automatically adds something like:
libfoo.so.1()(64bit)
Of course, I could still add a superfluous
Requires: libfoo
and then the resulting binary package would contain a redundant
dependency like this:
libfoo
libfoo.so.1()(64bit)
Has Fedora a policy against such redundant dependencies?
Best regards
Georg
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Sightly related to the topic, is there an effective way to use
pkgconfig(foo) for packages rather foo-devel? It seems very few
packages use that method.
Luya