From: Rich Lane <rlane@club.cc.cmu.edu>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] xapian-full and ncursesw gems
Date: Tue, 29 Dec 2009 18:58:05 -0500 [thread overview]
Message-ID: <1262127725-sup-1052@zyrg.net> (raw)
In-Reply-To: <1262127243-sup-4569@masanjin.net>
Excerpts from William Morgan's message of Tue Dec 29 18:00:52 -0500 2009:
> Reformatted excerpts from Rich Lane's message of 2009-12-28:
> > 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'.
AFAIK rubygems (at least in 1.9.1) works by adding (one version of) all
installed gems to the load path. Since I didn't rename any of the
ncurses gem files/directories "require 'ncursesw'" won't work - the main
file in lib/ is still ncurses.rb. Renaming the files seems like the
most logical thing to do so I'll push an update to the gem and send in a
Sup patch to try ncursesw first.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-29 23:58 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 [this message]
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=1262127725-sup-1052@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=sup-talk@rubyforge.org \
--cc=wmorgan-sup@masanjin.net \
/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