Skip to content

packaging issues - heroku/vulcan/kensa #40

Closed
aljosa opened this Issue Dec 3, 2012 · 1 comment

2 participants

@aljosa
aljosa commented Dec 3, 2012

using deb repository for heroku toolbelt doesn't work great w/ vulcan (and also kensa).
installing vulcan (gem install) also installs heroku gem and nothing actually works after that.

heroku-accounts plugin stops working, "vulcan create" doesn't work and it looks like it's all because "gem install vulcan" also installs heroku gem.

any way you could package everything into same package management so i can just do:
$ apt-get install heroku vulcan kensa
or
$ gem install heroku vulcan kensa

or update vulcan gem not to require heroku?

@wuputah
wuputah commented Dec 12, 2012

Vulcan's CLI currently uses the Heroku CLI internal directly. This is perhaps bad practice but I don't see this changing in the short term. See:
https://github.com/heroku/vulcan/blob/master/lib/vulcan/cli.rb#L3-L6
https://github.com/heroku/vulcan/blob/master/lib/vulcan/cli.rb#L140-L141

Your issue with the toolbelt can be fixed by making the directory with the toolbelt heroku binary occur in your PATH before your rubygems binary.

@wuputah wuputah closed this Dec 12, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.