> There are surely many dependency errors with libs.private because static
> linking is rarely attempted.
In distribution like Fedora, I'm not able to find even one case as none of the
source trees uses {Libs,Requires}.private so this issue is nor about rarity.
As you see the case which you been thinking that it may be in the collision
with what I've proposed is not something which could be used as the argument
against fixes proposed in this PR :)
If anywhere are used {Libs,Requires}.private .pc files dependencies there must
be only some custom made use cases which happen outside the area of any rpm
based distributions.
This is why I'm trying to convince to remove use --print-requires-private from
rpm vanilla source code.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/411#issuecomment-372441353_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
