From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] xapian-full and ncursesw gems
Date: Mon, 28 Dec 2009 18:12:54 -0500 [thread overview]
Message-ID: <1262035134-sup-4921@zyrg.net> (raw)
I've pushed two useful gems to gemcutter.
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.
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.
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.
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?
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-12-28 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 23:12 Rich Lane [this message]
2009-12-29 23:00 ` William Morgan
2009-12-29 23:58 ` Rich Lane
2009-12-30 0:06 ` William Morgan
2009-12-29 23:17 ` Tero Tilus
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=1262035134-sup-4921@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--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