I have 2 packages.
- eye a ruby process monitor https://github.com/chrisortman/habitat-plans/tree/master/eye
- a rails web app that I use eye to run 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?