--- Comment #69 from Jan Pokorný <> ---
But the client programs will likely use the pkgconfig dependency in the
build setup, and that has to be differentiated eventually in case it
cares about the protocol version.

> PKG_CHECK_MODULES(DBUS, libknet1, ...)

would make the specification targeted per the least surprise principle.
Otherwise versioning subpackages directly in the name is just half-baked
anticipation of future progress.

And then, RPM is automatically picking any pkgconfig files, turning
them into virtual "pkgconfig(X)" provides, i.e., fixed point in the
package dependencies graph (it was used to avoid file-based dependencies
hinted in [comment 28]), which is a concern from packaging perspective.

You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
package-review mailing list --
To unsubscribe send an email to

Reply via email to