From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs113738ebc; Mon, 25 Jan 2010 13:19:53 -0800 (PST) Received: by 10.91.49.5 with SMTP id b5mr2957341agk.82.1264454391359; Mon, 25 Jan 2010 13:19:51 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si12064066gxk.33.2010.01.25.13.19.50; Mon, 25 Jan 2010 13:19:51 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B62BB3C804D; Mon, 25 Jan 2010 16:19:50 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id D47E73C8044 for ; Mon, 25 Jan 2010 16:19:13 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NZWL3-0005Sx-J0 for sup-devel@rubyforge.org; Mon, 25 Jan 2010 16:19:13 -0500 From: William Morgan To: sup-devel mailing list Date: Mon, 25 Jan 2010 16:19:13 -0500 Message-Id: <1264454003-sup-9657@masanjin.net> User-Agent: Sup/git Subject: [sup-devel] Fwd: Re: Sup 0.10 released X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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? --- Begin forwarded message from Andrea Fazzi --- From: Andrea Fazzi To: ruby-talk Date: Mon, 25 Jan 2010 05:32:10 -0500 Subject: Re: Sup 0.10 released William Morgan wrote: > I'm pleased to announce the release of Sup 0.10. This version is > frickin' awesome because not only do we have Ruby 1.9 support, the > Xapian backend is now the default! The next version will discard Ferret > like a used rag. I had issues installing xapian-full gem on my ubuntu box running MRI ruby1.8. The installation fails building native extension even if it seems that all the C stuff get compiled correctly. BTW, I solved the issue in this way: sudo gem install xapian-full cd /usr/lib/ruby/gems/1.8/gems/xapian-full-1.1.3/ sudo rake build sudo mv xapian-full.gemspec ../../specifications/ andrea@ubuntu-desktop:~$ irb irb(main):001:0> require 'rubygems' => true irb(main):002:0> require 'xapian' => true Thanks for this great software! Cheers, Andrea --- End forwarded message --- -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel