search

cps-org / cps

Common Package Specification — A cross-tool mechanism for locating software dependencies
https://cps-org.github.io/cps/
Other
91 stars 8 forks source link

Better restrict and define search order #31

Closed dcbaker closed 4 months ago

dcbaker commented 5 months ago

I am much more interested in defining these rules explicitly than in what the rules are, though I think the changes I've made are reasonable. I have a major concern that multiple CPS implementers could make different decisions on how to sort these resulting in the same project, on the same exact machine, built with two different build systems, say CMake and Meson, picking different versions of the same project as a dependency. By specifying the search order, at the very least one implementation is "wrong" and it becomes more obvious who needs to change their implementation.

jonahbeckford commented 5 months ago

I very much agree that the sort order needs to be specified. But can we use semver (https://semver.org/) ordering?

mwoehlke commented 4 months ago

To be honest, I think not specifying details at this level was the intent, with the idea being to focus on getting some adoption (and usage experience) before tightening down on these sorts of minutia wherein it would be easy to make a decision that we end up regretting. That's not to say we should never do so, but I think there might be value in waiting.

dcbaker commented 4 months ago

I'm going to go ahead and close this for the time being. Given that we have cps-config as a de-facto of reference implementation, I feel a little more comfortable with the idea of not having this defined at this time.