Hi All,

Let you all know, I'm finally progressing on the build process. I sat
down last week determined to get this straightened out (it effects not
only this project, but a number of others too). After a lot of
deliberation I've nailed down the design and have transformed my
entire code base to suite. So I will have the build processes working
very soon --with the exception of win32 cross-compile for the moment,
b/c I accidentally deleted that script. :-(

The main insight I had is that there are really two sets of build
tasks. One that end-installers need access to, eg. compiling,
installing, rdoc generation and testing; and another set that is for
project admins, eg. publishing the website, packaging and pushing new
releases. To suite this, I simply converted the end-installer oriented
tasks in Ratch to pure Ruby and adopted them for Libxml. You can now
find them in the task/ directory in trunk.

The admin tasks on the other hand (which also include end-install
tasks) I reformulated into a simple "monolithic" project --thus
killing the original notion of Ratch (a collection of ruby-based batch
files). This new application is largely the resurrection of my earlier
work (reap). I will have an early release of the new  app out in a day
or two. With it, it is simply a matter to filling out the needed
metadata (yaml) files and calling the desired bin command. At the
moment there is an admin/ directory in trunk that house the old admin-
oriented tasks. Don't bother with these until I report having finished
the transition.

Btw.. I am getting a segfault on one file:

  $ task/test tests/tc_xml_node_copy.rb
  Loaded suite task/test
  Started
  ./tests/tc_xml_node_copy.rb:35: [BUG] Segmentation fault
  ruby 1.8.6 (2007-06-07) [i486-linux]

  Aborted (core dumped)

T.
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel

Reply via email to