On 20/01/2016 00:44, Daniel Quinn wrote: > I wanted to start fiddling with Heroku <https://heroku.com/>, so > naturally the first thing I tried was > > |$ eix heroku | > > …but alas there was nothing. So I poked around their site to see how one > might install their client manually and the instructions > <https://devcenter.heroku.com/articles/getting-started-with-python#set-up> > are the typically horrifying: > > |# wget -qO- https://toolbelt.heroku.com/install.sh | sh | > > The thing is, a quick look at what that || sh| is actually doing isn’t > all that terrifying. Basically it untars a bunch of ruby scripts into a > directory and then puts the path to the |heroku| “binary” (a ruby > script) in your $PATH. Surely, this is a good candidate for an ebuild, yes? > > So I thought I’d ask: am I missing something, or is this really as easy > as it looks? Is this just waiting for someone to write an ebuild? > Bugzilla has nothing > <https://bugs.gentoo.org/buglist.cgi?quicksearch=heroku> about it, but I > can’t believe that Heroku use hasn’t come up before in Gentoo land. > Surely there must be some web developers / ops people who would like to > use Heroku stuff from Gentoo…. right? > >
Some folks have worked on it but for whatever reason ebuilds never made it to the tree. The goddess has this to say: https://www.google.com/search?q=gentoo+ebuild+heroku&ie=utf-8&oe=utf-8 Or maybe they did and got tree cleaned. Search the old cvs Attic and see what used to be there. -- Alan McKinnon alan.mckin...@gmail.com
