Hi Andrei, These problems are all 1.9 related. But I'm very interested in getting Sup working with 1.9, so let's see if we can figure something out.
Reformatted excerpts from Andrei Thorp's message of 2011-01-25: > * use ruby-xapian-full You may not need this; see Rich's comments earlier. > * need gettext to be a gem and not a regular install... -- pacman -Rd > your ruby-gettext and sudo gem install ruby-gettext (STILL A PROBLEM, > SHOULD TALK TO THE MAINTAINER OF THAT PACKAGE) Perhaps the package has not been updated to 1.9? > * gem install sup: > - Won't install in local mode (i.e. into your ~), fyi (not that I care a > lot) What is ther error? Sup shouldn't care where its source files go. > - Still attempts to build ncurses (which fails)? Why's that? If I > override and install it without dependencies it seems to use ncursesw > happily enough. This is weird. Sup doesn't depend on the ncurses gem any more. And that gem doesn't build under 1.9. Sup now depends on the ncursesw gem (which Rich has been releasing newer versions of) which *does* support 1.9. > * The new package throws up this runtime error without a .sup directory: > > --- RuntimeError from thread: main > can't modify frozen string > /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/account.rb:54:in > `force_encoding' This is the most troubling. I will see if I can figure out what's going on here. I've seen this before and it's another symptom of Ruby 1.9 string insanity. > The above I've seen to be bug 98 on the bugtracker... but for whatever > reason, the bugtracker has been down for a week or two on my end. Due to spam reasons I've shut it down, at least for the time being. > What xapian package do you recommend using? Maybe that's the source of > my problems. I suspect not, given the above. -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
