1 |
I wanted to start fiddling with Heroku <https://heroku.com/>, so |
2 |
naturally the first thing I tried was |
3 |
|
4 |
|$ eix heroku | |
5 |
|
6 |
…but alas there was nothing. So I poked around their site to see how one |
7 |
might install their client manually and the instructions |
8 |
<https://devcenter.heroku.com/articles/getting-started-with-python#set-up> |
9 |
are the typically horrifying: |
10 |
|
11 |
|# wget -qO- https://toolbelt.heroku.com/install.sh | sh | |
12 |
|
13 |
The thing is, a quick look at what that || sh| is actually doing isn’t |
14 |
all that terrifying. Basically it untars a bunch of ruby scripts into a |
15 |
directory and then puts the path to the |heroku| “binary” (a ruby |
16 |
script) in your $PATH. Surely, this is a good candidate for an ebuild, yes? |
17 |
|
18 |
So I thought I’d ask: am I missing something, or is this really as easy |
19 |
as it looks? Is this just waiting for someone to write an ebuild? |
20 |
Bugzilla has nothing |
21 |
<https://bugs.gentoo.org/buglist.cgi?quicksearch=heroku> about it, but I |
22 |
can’t believe that Heroku use hasn’t come up before in Gentoo land. |
23 |
Surely there must be some web developers / ops people who would like to |
24 |
use Heroku stuff from Gentoo…. right? |
25 |
|
26 |
|