Regardless of whether we publish gems, we still have dependencies on custom builds of gems that will never be public. chef v11.6.0.2 will always be a private build only available from our right_link gem source. Personally, I see no value to publishing right_git, etc., because I am not looking for more maintenance jobs for teal to do. If someone tells me there it is important to update rubygems then I will take the time to do it. In the meantime, ungitting the gems works regardless of whether they come from the rubygems or right_link gem source so long as the gem exists in right_link gem source.

That being said, the package building for both Linux and Windows works okay for gitted gems (with the exception of the chef/chef directory not being understood for chef v10 and previous). With chef v11 they eliminated that issue by only having the chef gem in the chef repository so all of our custom build gems can remain gitted EXCEPT for those which build natively for Windows. bundler doesn't understand natively-built gems so pre-built gems like eventmachine v1.0.0.4 cannot be gitted in the Gemfile.