Hmm. Changing the gem names is causing to cause problems because
you might think you've upgraded to libxml version 7, but in fact
you're still pulling in libxml-ruby version 2. I see no way around
that.
Maybe the thing to do is change the name for Ruby 1.9. For libxml-
ruby require a ruby version of less than 1.9, for libxml require a
ruby version of 1.9 or greater. If that is doable (not sure it is),
then at least you can't have a conflict.
Actually, that's a great idea. Changing the install name for 1.9
works since everyone will have to reinstall and that's something
that's done at make/extconf.rb time not run time. -sc
--
Sean Chittenden
[EMAIL PROTECTED]
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
