Should the dependency for chef be implied?

[jamietanna]

I'm not sure if this is how I'm consuming this Gem, but adding the dependency when installing into the Chef Workstation through either chef gem or Bundler leads to my Gems attempting to upgrade the version of Chef, due to the unversioned dependency on chef

I wonder if we could make it an implicit dependency (i.e. don't add it as an add_dependency) so it installs nicely?

Or is there a better way of doing this?

[realityforge]

To be honest I am not entirely sure. The way we have done in it in the past is to lock down the version of chef in the Gemfile on the workstation.

[jamietanna]

Interesting that's how I'd been doing it too, but finding that, by using a Gemfile and it pulling other dependencies, other Chef versions get pulled, so I'd have to pin all the versions from the workspace.

What do you think about a, maybe prerelease, version without it pinned to see how that works?