Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Hamish D <dmishd@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] try heliotrope!
Date: Mon, 27 Jun 2011 10:52:14 +0100	[thread overview]
Message-ID: <BANLkTi=MnULdUFhw8Vf5=0dSL_VrbDGLvQ@mail.gmail.com> (raw)
In-Reply-To: <1309152077-sup-5963@masanjin.net>

> If any of you are interested in trying out the next generation of Sup, I
> have things in a reasonably stable state. It's still too early for a
> gem, but I have updated the README for both client and server sides.

Couple of broken bits in the READMEs

turnsole/README - lists rubymail as a gem to instal - should that be rmail ?

heliotrope/README - lists leveldb as a gem but gem didn't find it. A
gem search finds leveldb-ruby instead.

And does heliotrope use both leveldb and whistlepig, or just one of
them? (I didn't follow the recent discussion that closely I'm afraid).

Then the gem install of leveldb-ruby failed aswell. So I re-read your
discussion with Horacio and I see the same issue (-fPIC related - I am
also on Ubuntu 11.04). You mention that leveldb-ruby 0.5 should be
available, but I only found 0.4 through gem search -r ...

Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-06-27 10:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  5:36 William Morgan
2011-06-27  9:52 ` Hamish D [this message]
2011-06-28  3:53   ` William Morgan
2011-06-28 18:34     ` Hamish Downer
2011-06-28 20:40       ` William Morgan
2011-06-28 21:18         ` Alvaro Herrera
2011-06-27 15:02 ` [sup-talk] " Kevin Mark
2011-06-27 21:30 ` sergeig
2011-06-28  3:54   ` William Morgan
2011-06-28  3:32 ` [sup-devel] " William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTi=MnULdUFhw8Vf5=0dSL_VrbDGLvQ@mail.gmail.com' \
    --to=dmishd@gmail.com \
    --cc=sup-devel@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox