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
