Curiously, I use ruby 1.8.3 + instiki 0.10.2 on Ubuntu Breezy, and it seems to work without throwing this error. I wonder why? Does it somehow pick up the 0.13.1 rails I have installed on the system in preference to the old broken one that ships with it? I haven't had time to investigate.Hi Ben, Thanks muchly for the update. I am actually a debian (Ubuntu) usermyself. Love the system, hate what they did to Ruby - just didn't havetime to catch up on updates as much as I should :-) Cheers,Assaph
Fragmentation of ruby into individual libruby* packages is, I think, a necessary evil on a Debian system. However, the fragmentation doesn't have to be as aggressive as it was initially, and I believe that has been remedied already.
The other contentious issue was rubygems. The trouble is, ruby's goals for rubygems, and Debian's goals with their packaging system are somewhat at odds with each other. But I don't think either side deliberately wants to make it hard for each other, so I remain optimistic that we'll work out a mutually agreeable compromise.
In short, although ruby and Debian's relationship had a rocky start, it looks like things are stabilizing, so that running ruby applications on Debian won't have to be a pulling-hair-out-at-the-roots experience.
Ben
_______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
