From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Fwd: Re: Sup 0.10 released
Date: Mon, 25 Jan 2010 17:05:49 -0500 [thread overview]
Message-ID: <1264456949-sup-3@zyrg.net> (raw)
In-Reply-To: <1264454003-sup-9657@masanjin.net>
Excerpts from William Morgan's message of 2010-01-25 16:19:13 -0500:
> I'm seeing a weird behavior with the xapian-full gem, and so is this
> guy. The installation claims it fails, but it actually succeeds. The
> spec file is not copied over after installation, so `gem list` doesn't
> show it, but if you require 'xapian' it actually does pick up the code,
> even after the failed installation.
>
> Ideas?
This has been reported before but I haven't figured out what's going on.
I pushed the source of the xapian-full gem to git://github.com/rlane/xapian-full
in case anyone else wants to take a crack at this.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-01-25 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 21:19 William Morgan
2010-01-25 22:05 ` Rich Lane [this message]
2010-01-25 23:37 ` Rich Lane
2010-01-26 0:21 ` Mark Alexander
2010-01-26 0:35 ` Rich Lane
2010-01-26 13:22 ` William Morgan
2010-01-26 15:50 ` Nicolas Pouillard
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=1264456949-sup-3@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--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