You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to ease adoption, it would be helpful if CPS provided a way to specify dependencies on things which are not described by CPS. In particular, pkg-config is a likely target for such a feature.
I propose adding a provider attribute to <requirement> objects, with supported values cps and pkgconf.
A value of pkgconf shall inform tools to search for <name>.pc, which shall provide the component(s) <name>:shared and/or <name>:static. The tool shall respect the version and components attributes in the usual fashion.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In order to ease adoption, it would be helpful if CPS provided a way to specify dependencies on things which are not described by CPS. In particular, pkg-config is a likely target for such a feature.
I propose adding a
provider
attribute to<requirement>
objects, with supported valuescps
andpkgconf
.A value of
pkgconf
shall inform tools to search for<name>.pc
, which shall provide the component(s)<name>:shared
and/or<name>:static
. The tool shall respect theversion
andcomponents
attributes in the usual fashion.Beta Was this translation helpful? Give feedback.
All reactions