Specifying tool versioning in the Bender.yml manifest file

[oxcabe]

Description

Allow package maintainers to declare the toolset the project uses could be helpful for other maintainers and users. The idea is to have a concise, standardised approach that initially is purely informative, but could be leveraged by this project or third-party tooling (e.g. CycloneDX tooling).

I came up with this while having a look at pulp-c910, as I couldn't find any high-level details that helped me understand which SystemVerilog version is being used there.

Relevant approaches

• The engines field in package.json spec.
• The build-system table in pyproject.toml spec.

Additional details

I'd gladly help integrating something like this, in case you find this feature relevant and interesting to have. A good starter point would be to discuss if there's something else we'd like to have this for, and possibly define non-goals for things that shouldn't be covered through this feature.

[micprog]

Bender is designed to be fairly agnostic and not enforce what tools or versions thereof to use. Nonetheless, I see your point in specifying which standard the repo is designed to, and what tools are expected to work with it. I think it might make more sense to keep this separate from bender itself.