From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup-server revisited
Date: Sat, 26 Feb 2011 19:15:40 +0000 [thread overview]
Message-ID: <1298744738-sup-631@whisper> (raw)
In-Reply-To: <1298320404-sup-5972@masanjin.net>
Excerpts from William Morgan's message of Mon Feb 21 21:02:28 +0000 2011:
> As I alluded to in an earlier email to sup-devel, I have been working recently
> on the ancient goal of splitting Sup functionality out into separate client and
> server programs. This will have many advantages; in particular it will remove
> email lock-in by making it possible to have non-Sup clients interact with Sup.
Excellent :) I look forward to an android client. I will definitely
contribute to it, and I *might* even get it started. Or might not ...
> You can find the work in progress here: https://github.com/wmorgan/heliotrope
> Currently it is not actually a server, but accomplishes many of the goals
> above. Run bin/email-indexer and then bin/email-searcher to play around with
> a simple preview of things to come. Stay tuned for more on this.
I've had a quick look at heliotrope (and whistlepig) and not got very
far:
$ ruby -I lib bin/email-indexer ~/path/to/mbox
/var/lib/gems/1.8/gems/ffi-1.0.6/lib/ffi/library.rb:93:in `ffi_libraries': no library specified (LoadError)
from /var/lib/gems/1.8/gems/ffi-1.0.6/lib/ffi/library.rb:129:in `attach_function'
from /var/lib/gems/1.8/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/utilities.rb:39:in `func'
from /var/lib/gems/1.8/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/utilities.rb:214
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /var/lib/gems/1.8/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/extensible_string/c.rb:1
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /var/lib/gems/1.8/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/extensible_string.rb:1
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /var/lib/gems/1.8/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/hash_database.rb:2
from /var/lib/gems/1.8/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer.rb:11:in `open'
from ./lib/heliotrope/store.rb:40:in `initialize'
from bin/email-indexer:20:in `new'
from bin/email-indexer:20
$ ruby --version
ruby 1.8.7 (2010-06-23 patchlevel 299) [x86_64-linux]
Am I missing something? It appears that the oklahoma_mixer gem is
broken. I installed it though rubygems. Any ideas?
I also wasn't sure how to build and run whistlepig from source. I'm not
familiar with the extconf stuff. I can type make happily enough, but it
appears more steps are required. If someone shows me the way I'll
happily contribute an improved README for anyone else who wants to use
it. (I installed whistlepig from the gem in order to try out heliotrope,
in case you're wondering).
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-02-26 19:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 21:02 William Morgan
2011-02-22 13:46 ` Mark Alexander
2011-02-22 17:55 ` William Morgan
2011-02-22 18:44 ` Tero Tilus
2011-02-22 19:00 ` William Morgan
2011-02-22 14:09 ` Nicolas Pouillard
2011-02-22 20:17 ` Tero Tilus
2011-02-22 21:29 ` William Morgan
2011-02-23 9:48 ` Nicolas Pouillard
2011-02-23 18:43 ` William Morgan
2011-02-23 18:53 ` Alvaro Herrera
2011-02-23 21:08 ` William Morgan
2011-02-23 21:30 ` Alvaro Herrera
2011-03-03 19:38 ` Sascha Silbe
2011-02-26 19:15 ` Hamish [this message]
2011-02-26 22:04 ` William Morgan
2011-02-26 23:15 ` William Morgan
2011-03-01 19:38 ` Hamish
2011-03-02 12:43 ` Gregor Hoffleit
2011-03-02 18:51 ` William Morgan
2011-03-03 17:32 ` Gregor Hoffleit
2011-03-03 19:17 ` William Morgan
2011-04-15 10:46 ` Gregor Hoffleit
2011-04-15 17:16 ` William Morgan
2011-04-15 20:53 ` Gregor Hoffleit
2011-04-17 16:58 ` William Morgan
2011-04-17 17:55 ` 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=1298744738-sup-631@whisper \
--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