[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sup-talk] xapian-full and ncursesw gems



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 <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk