On Jul 7, 2:54 am, Charlie Savage <[EMAIL PROTECTED]> wrote: > To go with the new libxml-ruby release, I've pushed up a libxslt-ruby > release.
I'm glad to see libxslt library getting some loving, it was sorely in need of it. Some months ago we discussed this with regards to libxml. The same applies to libxslt. That is, the name needs to transition to "libxslt", dropping the "-ruby". > It includes two big changes. > > * Windows support (both lots of memory fixes and binaries) > > * New libxslt.rb ruby wrapper, so programs can simply say: > > require 'libxslt' > > * For all other platforms, I updated extconf.rb to tell gcc that > libxslt-ruby depends on libxml-ruby being present. To do this trick, I > made a big assumption - that libxml-ruby is installed as a gem. I did > this because I couldn't figure out any other way to reliably determine > where the libxml-ruby header files were on disk. What do people think o > of this? I'll take a peak at it as soon as I finish up what I working on at the moment (in a couple of days). > Last, the project name on rubyforge is libxsl which is incorrect. It > should be libxslt since its wrapping the libxslt library > (http://xmlsoft.org/XSLT/). Is it possible to change names? That would require creating a new rubyforge project. Do you think it's worth the transition? T. _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
