From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] xapian-full and ncursesw gems
Date: Wed, 30 Dec 2009 01:17:59 +0200 [thread overview]
Message-ID: <1262127955-sup-7589@tilus.net> (raw)
In-Reply-To: <1262035134-sup-4921@zyrg.net>
Rich Lane, 2009-12-29 01:12:
> ncursesw: This is a version of the ncurses gem modified to link
> against the ncursesw library so you get wide character support.
Rich rocks! \o/
> The only thing I worry about here is users lacking the full
> toolchain required to build Xapian.
Doesn't sound bad to me. How tough a requirement "full toolchain
required to build Xapian" really is? What platforms would be
problematic?
> 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. Thoughts?
If you say "don't you dare to require both ncurses and ncursesw" in
README and make ncursesw complain if ncurses is already required I'd
say it's as good a gem-citizen as it gets. Then just (as William
already said) make sup try ncursesw first and fall back to ncurses if
it fails.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-12-29 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 23:12 Rich Lane
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 [this message]
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=1262127955-sup-7589@tilus.net \
--to=tero@tilus.net \
--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