From: Anthony Martinez <pi+sup@pihost.us>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-talk <sup-talk@rubyforge.org>, sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [sup-talk] Ferret to Xapian conversion
Date: Sun, 03 Jan 2010 15:47:39 -0700 [thread overview]
Message-ID: <1262558818-sup-5188@home.mrtheplague.net> (raw)
In-Reply-To: <1262549410-sup-7918@zyrg.net>
Excerpts from Rich Lane's message of Sun Jan 03 13:18:35 -0700 2010:
> Excerpts from Anthony Martinez's message of 2010-01-03 14:38:52 -0500:
> > Speaking of not having the Xapian gem, when I tried "gem install xapian-full",
> > it looked like it worked, but didn't actually install a gem on my system. Here's
> > the build log: http://pastebin.com/f2d25a13c
>
> I noticed that gem thinks the xapian compile failed, but it actually
> succeeded and since it was in-place the installed gem worked fine.
I don't know enough about packaging Gems to help out, unfortunately. The way I'm
proceeding for now is to add "-I /var/lib/gems/1.8/gems/xapian-full-1.1.3/lib/"
to my Ruby command line (and in the case of the conversion script, to the
RUBY_INVOCATION environment). Life is ridiculous. :)
It appears to have worked, though, as I'm now writing this from a
Xapian-indexed sup!
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-01-03 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1262460996-sup-1383@home.mrtheplague.net>
[not found] ` <1262467343-sup-9565@masanjin.net>
[not found] ` <1262471675-sup-1708@masanjin.net>
[not found] ` <1262531773-sup-5192@masanjin.net>
2010-01-03 19:38 ` Anthony Martinez
2010-01-03 20:18 ` Rich Lane
2010-01-03 22:47 ` Anthony Martinez [this message]
2010-01-03 22:07 ` 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=1262558818-sup-5188@home.mrtheplague.net \
--to=pi+sup@pihost.us \
--cc=rlane@club.cc.cmu.edu \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@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