# Resolving transitive runtime dependencies

**URL:** <https://discourse.chef.io/t/resolving-transitive-runtime-dependencies/18839>\
**Category:** Habitat Help\
**Created:** [June 26, 2018, 1:56pm UTC](https://discourse.chef.io/t/resolving-transitive-runtime-dependencies/18839 "2018-06-26T13:56:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisortman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/chrisortman/32/3015_2.png) [@chrisortman](https://discourse.chef.io/u/chrisortman)\
**Post date:** [June 26, 2018, 1:56pm UTC](https://discourse.chef.io/t/resolving-transitive-runtime-dependencies/18839/1 "2018-06-26T13:56:35Z")

</div>

I have 2 packages.

1. eye a ruby process monitor [https://github.com/chrisortman/habitat-plans/tree/master/eye](https://github.com/chrisortman/habitat-plans/tree/master/eye)
2. a rails web app that I use eye to run [https://github.com/ui-icts/sparc-request/tree/master/habitat/sparc-request-base](https://github.com/ui-icts/sparc-request/tree/master/habitat/sparc-request-base)

**I do this so that I can have a single habitat package that spins up both puma and delayed\_job processes**

My eye package depends on core/ruby (currently 2.5.1)  
My rails app depends on core/ruby/2.4.2 **and** on chrisortman/eye

When I build my rails app, it errors because of the conflict between the ruby dependencies. Assuming I’ve done all the PATH, GEM\_HOME, GEM\_PATH gymnastics, I should be able to run eye with ruby 2.5.1 and have it launch puma with ruby 2.4.2

My question, can I void the warranty and tell habitat this is ok to build?

---

<div class="post-metadata">

**Author:** ![elliott-davis](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/elliott-davis/32/2146_2.png) [@elliott-davis](https://discourse.chef.io/u/elliott-davis)\
**Post date:** [June 26, 2018, 1:59pm UTC](https://discourse.chef.io/t/resolving-transitive-runtime-dependencies/18839/2 "2018-06-26T13:59:47Z")

</div>

I think it should be okay ™

If you are getting conflicts out of the plan-build dep-solver I’m not sure how you’d work around it though.

---

<div class="post-metadata">

**Author:** ![chrisortman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/chrisortman/32/3015_2.png) [@chrisortman](https://discourse.chef.io/u/chrisortman)\
**Post date:** [June 26, 2018, 2:03pm UTC](https://discourse.chef.io/t/resolving-transitive-runtime-dependencies/18839/3 "2018-06-26T14:03:20Z")

</div>

Yeah, that’s the problem is that I can’t build the package because it detects these conflicts

---

<div class="post-metadata">

**Author:** ![chrisortman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/chrisortman/32/3015_2.png) [@chrisortman](https://discourse.chef.io/u/chrisortman)\
**Post date:** [June 26, 2018, 2:06pm UTC](https://discourse.chef.io/t/resolving-transitive-runtime-dependencies/18839/4 "2018-06-26T14:06:23Z")

</div>

Ultimately I think I’ll build a package that links against the old version of ruby because that is probably the simplest thing to do.

This pattern seems to creep up once in a while though (I think bundler comes to mind) where I want a package for the ruby gem but now you have competing requests for which version of ruby to link to.  
Maybe it would make sense for me to make a my-ruby-with-deps package
