Ok, I think I've got the intent.
The flaw in the approach is that the namespace of pkg-config (and likely
Python/rust/perl/node/Java etc) is very different than rpm package names and a
fully general solution would need to supply mappings between "package"
namespaces that are deliberately using different string identifiers.
Mapping between namespaces is a much harder problem to solve than passing NEVRA
identifiers to helpers through either macros or envvars.
Note that a fully general mapping mechanism might also unify rpm and apt/dpkg
dependency namespaces and simplify interoperation.
--
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/issues/502#issuecomment-412372183
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
