From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.87.14 with SMTP id k14cs1197116agb; Tue, 29 Dec 2009 15:01:07 -0800 (PST) Received: by 10.224.31.77 with SMTP id x13mr8331895qac.130.1262127666144; Tue, 29 Dec 2009 15:01:06 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 39si19549497qyk.16.2009.12.29.15.01.06; Tue, 29 Dec 2009 15:01:06 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id EA80D1D78862; Tue, 29 Dec 2009 18:01:05 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 3B4B116782B6 for ; Tue, 29 Dec 2009 18:00:53 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NPl3d-0007nl-0e for sup-talk@rubyforge.org; Tue, 29 Dec 2009 15:00:53 -0800 From: William Morgan To: sup-talk In-reply-to: <1262035134-sup-4921@zyrg.net> References: <1262035134-sup-4921@zyrg.net> Date: Tue, 29 Dec 2009 15:00:52 -0800 Message-Id: <1262127243-sup-4569@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] xapian-full and ncursesw gems X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup 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-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Reformatted excerpts from Rich Lane's message of 2009-12-28: > xapian-full: This is based on the existing xapian gem, but compiles > xapian-core as well as the bindings so it isn't dependent on the version > of the system xapian. It's also a newer development version that > includes the Chert backend. Awesome! > ncursesw: This is a version of the ncurses gem modified to link > against the ncursesw library so you get wide character support. It > also includes the ruby 1.9.1 compile fixes. Awesome! Thanks for doing this. This will bring us singificantly closer to solving two of the most common problems (my ferret index crashed / my non-ASCII chars look funny) out of the box. > When we switch the default index to Xapian, for ease of installation I > think we should add xapian-full as a gem dependency even though it may > be redundant with a system xapian install. The only thing I worry > about here is users lacking the full toolchain required to build > Xapian. I'm fine with this, especially if the Chert backend is significantly better. > One potential problem with the ncursesw gem is that I've kept source > compatibility with the old ncurses gem by not renaming the > files/module. This means they interact badly if both are installed. We > could change the Sup source to use new ncursesw names, but that's > annoying and breaks people doing "git pull". Thoughts? I think keeping source compatibility is a good idea. The conflict only happens if both gems are loaded, so Sup can require 'ncursesw', and then fall back to 'ncurses'. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk