wrote:
>
>
> Please send me a documentation paragraph that I can add to .find
> which
> makes this more explicit and understandable. Hopefully this will
> eliminate future confusion over the usage.
>
> There is a little bit of documentation, but it's in the XPath class, which
> takes a little tracking down. It doesn't help the the XPath rdocs are
> messed
> up: the doc for .find ends up in XML::XPath::InvalidPath for reasons I
> haven't been able to ferret out.
>
> Here's a patch that tries to explain things, as applied to the XPath file.
> (I haven't looked too hard into why this is getting put in the wrong
> place,
> though I guess I could.) This could be moved in whole to the Node class if
> desired or a pointer from the Node class to the XPath class.
>
> Index: ext/libxml/ruby_xml_xpath.c
> ===================================================================
> --- ext/libxml/ruby_xml_xpath.c (revision 242)
> +++ ext/libxml/ruby_xml_xpath.c (working copy)
> @@ -99,8 +99,8 @@
> * call-seq:
> * XML::XPath.find(path, namespaces = [any]) => xpath
> *
> - * Find nodes matching the specified xpath (and optionally any of the
> - * supplied namespaces) and return as an XML::Node::Set.
> + * Find nodes matching the specified xpath and return as an
> + * XML::Node::Set.
> *
> * The optional namespaces argument may take one of
> * two forms:
> @@ -109,9 +109,33 @@
> * * An array of:
> * * strings in the form like above
> * * arrays in the form of ['prefix','uri']
> - *
> - * If not specified, matching nodes from any namespace
> - * will be included.
> + *
> + * For example, to match the elements in the XHTML document
> + *
> + *
> + *
> + *
> + * you could write
> + * doc.find "//x:p", "x:http://www.w3.org/1999/xhtml"
> + *
> + * Two very commonly asked questions are:
> + *
> + * * How do I match nodes that use the default namespace prefix
> +
> + * The example shows how to do this. Even though the default namespace
> + * prefix is used in the document, the xpath expression must
> + * explicitly identify the namespace. The only nodes that a pattern
> + * without a namespace will match are nodes that do not have a
> + * namespace, neither explicit nor from a default prefix.
> + *
> + * * How do I match particular nodes within any namespace
> + *
> + * It is possible to match all nodes with the star pattern, e.g.,
> + * //*, and it is possible to match all nodes within an
> + * individual namespace, e.g., //ns:*, but it is not possible
> + * to match individual nodes from any namespace: //*:p is
> + * invalid.
> + *
> */
> VALUE
> ruby_xml_xpath_find(VALUE class, VALUE anode, VALUE xpath_expr, VALUE
> nslist) {
>
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/libxml-devel/attachments/20080122/cfd3998c/attachment.html
From transfire at gmail.com Tue Jan 22 13:54:53 2008
From: transfire at gmail.com (Trans)
Date: Tue, 22 Jan 2008 10:54:53 -0800 (PST)
Subject: [libxml-devel] finally closing in on the new build
Message-ID: <9ddcb8d9-fbb3-4d37-ac2e-d88e6963473a@k2g2000hse.googlegroups.com>
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.
From Glenn.McCord at gmail.com Wed Jan 23 16:31:06 2008
From: Glenn.McCord at gmail.com (GlennNZ)
Date: Wed, 23 Jan 2008 13:31:06 -0800 (PST)
Subject: [libxml-devel] Unusual runtime termination
Message-ID: <860f9f23-fb01-4fab-8e28-360e7a562ee4@l1g2000hsa.googlegroups.com>
I was putting off posting this but I've decided to cover all bases.
I'm using the libxml ruby bindings under windows courtesy of the
compilation available from http://www.movesonrails.com/articles/2007/10/09/libxml-ruby-and-windows
However, when using the library, I'm getting an error, which appears
to intermittent.
"This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information."
Googling this error refers to a whole lot of Microsoft related errors
which leads me to believe that the something has happened during
compilation of library. On the off chance that this error has happened
to someone else, please reply so that I don't feel inclined to try and
compile xmllib using Visual Studio myself.
The error appears to be intermittent in that if I have some code that
parses an XML file, loads a schema, validates against the schema and
then does some simple dom traversal, then I will get the error about 2
out of 5 times.
If I load another XML file further into the program, then I will
likely always get the error, and the chances are it stuffs something
up.
Cheers to anyone who is familar with this.
From stuart at smgsystems.co.uk Mon Jan 28 09:51:40 2008
From: stuart at smgsystems.co.uk (Stuart Grimshaw)
Date: Mon, 28 Jan 2008 14:51:40 +0000
Subject: [libxml-devel] Unable to install libxml gem on Debian.
Message-ID:
Hi,
I'm trying to install the libxml-ruby gem on my debian server, without
much luck.
You can view the output here:
http://www.trafficjammr.co.uk/mkmf.log
but let me know if there's ny more info you need.
--
-S
Follow me on Twitter: http://twitter.com/stubbs
Buy my photos: http://stuartgrimshaw.imagekind.com
Blog: http://stubblog.wordpress.com
From rubys at intertwingly.net Tue Jan 29 13:59:30 2008
From: rubys at intertwingly.net (Sam Ruby)
Date: Tue, 29 Jan 2008 13:59:30 -0500
Subject: [libxml-devel] prepping libxml2 for Ruby 1.9?
Message-ID: <479F7792.20406@intertwingly.net>
Two things:
I'm trying to port a number of projects to Ruby 1.9. Current status can
be seen here:
http://intertwingly.net/projects/ruby19/logs/
I'd like to try libxml2, presuming that people would be interested in
accepting patches to make this work under 1.9, while continuing to work
under 1.8.
The second thing is that I first tried to build it under 1.8. What I
get is:
$ rake
(in /home/rubys/svn/libxml)
rake aborted!
No such file or directory - ext/xml/libxml.h
/home/rubys/svn/libxml/Rakefile:18:in `read'
(See full trace by running task with --trace)
Did I miss a step?
- Sam Ruby
From smparkes at smparkes.net Tue Jan 29 15:25:49 2008
From: smparkes at smparkes.net (Steven Parkes)
Date: Tue, 29 Jan 2008 12:25:49 -0800
Subject: [libxml-devel] prepping libxml2 for Ruby 1.9?
In-Reply-To: <479F7792.20406@intertwingly.net>
References: <479F7792.20406@intertwingly.net>
Message-ID: <870667EBED5D44DC99CFCE3F35CBFE25@windows.esseff.org>
$ rake
(in /home/rubys/svn/libxml)
rake aborted!
No such file or directory - ext/xml/libxml.h
At last mention, trunk was in flux:
http://groups.google.com/group/libxml-devel/browse_thread/thread/b044e502102
d2c37
and apparently won't be using rake anymore.
From transfire at gmail.com Wed Jan 30 17:30:58 2008
From: transfire at gmail.com (Trans)
Date: Wed, 30 Jan 2008 14:30:58 -0800 (PST)
Subject: [libxml-devel] prepping libxml2 for Ruby 1.9?
In-Reply-To: <479F7792.20406@intertwingly.net>
References: <479F7792.20406@intertwingly.net>
Message-ID: <7592bb30-0d0a-4c41-97ad-a4f6ace9c895@i7g2000prf.googlegroups.com>
On Jan 29, 1:59 pm, Sam Ruby wrote:
> Two things:
>
> I'm trying to port a number of projects to Ruby 1.9. Current status can
> be seen here:
>
> http://intertwingly.net/projects/ruby19/logs/
>
> I'd like to try libxml2, presuming that people would be interested in
> accepting patches to make this work under 1.9, while continuing to work
> under 1.8.
>
> The second thing is that I first tried to build it under 1.8. What I
> get is:
>
> $ rake
> (in /home/rubys/svn/libxml)
> rake aborted!
> No such file or directory - ext/xml/libxml.h
> /home/rubys/svn/libxml/Rakefile:18:in `read'
> (See full trace by running task with --trace)
>
> Did I miss a step?
$ task/make
T.
From rubys at intertwingly.net Wed Jan 30 17:39:32 2008
From: rubys at intertwingly.net (Sam Ruby)
Date: Wed, 30 Jan 2008 17:39:32 -0500
Subject: [libxml-devel] prepping libxml2 for Ruby 1.9?
In-Reply-To: <7592bb30-0d0a-4c41-97ad-a4f6ace9c895@i7g2000prf.googlegroups.com>
References: <479F7792.20406@intertwingly.net>
<7592bb30-0d0a-4c41-97ad-a4f6ace9c895@i7g2000prf.googlegroups.com>
Message-ID: <47A0FCA4.2000604@intertwingly.net>
Trans wrote:
>
> On Jan 29, 1:59 pm, Sam Ruby wrote:
>> Two things:
>>
>> I'm trying to port a number of projects to Ruby 1.9. Current status can
>> be seen here:
>>
>> http://intertwingly.net/projects/ruby19/logs/
>>
>> I'd like to try libxml2, presuming that people would be interested in
>> accepting patches to make this work under 1.9, while continuing to work
>> under 1.8.
>>
>> The second thing is that I first tried to build it under 1.8. What I
>> get is:
>>
>> $ rake
>> (in /home/rubys/svn/libxml)
>> rake aborted!
>> No such file or directory - ext/xml/libxml.h
>> /home/rubys/svn/libxml/Rakefile:18:in `read'
>> (See full trace by running task with --trace)
>>
>> Did I miss a step?
>
> $ task/make
OK, that builds a .so file. What setup do I need to run tast/test? I'm
getting a lot of Error loading: tests/tc_* messages currently.
- Sam Ruby
From transfire at gmail.com Wed Jan 30 17:40:14 2008
From: transfire at gmail.com (Trans)
Date: Wed, 30 Jan 2008 14:40:14 -0800 (PST)
Subject: [libxml-devel] .deb packages needed to compile
Message-ID:
It would be nice to enumerate all the extra debian/ubuntu packages
needed to compile libxml2-ruby.
So far I know of:
libxml2
libxml2-dev
libz-dev
What are the others?
T.
From transfire at gmail.com Wed Jan 30 17:47:18 2008
From: transfire at gmail.com (Trans)
Date: Wed, 30 Jan 2008 14:47:18 -0800 (PST)
Subject: [libxml-devel] prepping libxml2 for Ruby 1.9?
In-Reply-To: <47A0FCA4.2000604@intertwingly.net>
References: <479F7792.20406@intertwingly.net>
<7592bb30-0d0a-4c41-97ad-a4f6ace9c895@i7g2000prf.googlegroups.com>
<47A0FCA4.2000604@intertwingly.net>
Message-ID: <24545c4f-addc-43fd-8496-5a36ec37cdd1@i72g2000hsd.googlegroups.com>
On Jan 30, 5:39 pm, Sam Ruby wrote:
> Trans wrote:
>
> > On Jan 29, 1:59 pm, Sam Ruby wrote:
> >> Two things:
>
> >> I'm trying to port a number of projects to Ruby 1.9. Current status can
> >> be seen here:
>
> >>http://intertwingly.net/projects/ruby19/logs/
>
> >> I'd like to try libxml2, presuming that people would be interested in
> >> accepting patches to make this work under 1.9, while continuing to work
> >> under 1.8.
>
> >> The second thing is that I first tried to build it under 1.8. What I
> >> get is:
>
> >> $ rake
> >> (in /home/rubys/svn/libxml)
> >> rake aborted!
> >> No such file or directory - ext/xml/libxml.h
> >> /home/rubys/svn/libxml/Rakefile:18:in `read'
> >> (See full trace by running task with --trace)
>
> >> Did I miss a step?
>
> > $ task/make
>
> OK, that builds a .so file. What setup do I need to run tast/test? I'm
> getting a lot of Error loading: tests/tc_* messages currently.
Ah... in task/test change the line:
$LOAD_PATH.unshift(File.expand_path('ext/libxml')) unless live
to:
unless live
$LOAD_PATH.unshift(File.expand_path('ext/libxml'))
$LOAD_PATH.unshift(File.expand_path('lib'))
end
BTW, to compile and install it is:
$ task/setup
This is a minor variation on Minero Aoki setup.rb, so anything you
could do with setup.rb you can do with task/setup.
T.
From transfire at gmail.com Thu Jan 31 08:08:59 2008
From: transfire at gmail.com (Trans)
Date: Thu, 31 Jan 2008 05:08:59 -0800 (PST)
Subject: [libxml-devel] prepping libxml2 for Ruby 1.9?
In-Reply-To: <479F7792.20406@intertwingly.net>
References: <479F7792.20406@intertwingly.net>
Message-ID: <378860ba-408c-4434-9485-28c4f12c98cf@v4g2000hsf.googlegroups.com>
On Jan 29, 1:59 pm, Sam Ruby wrote:
> Two things:
>
> I'm trying to port a number of projects to Ruby 1.9. Current status can
> be seen here:
>
> http://intertwingly.net/projects/ruby19/logs/
>
> I'd like to try libxml2, presuming that people would be interested in
> accepting patches to make this work under 1.9, while continuing to work
> under 1.8.
>
> The second thing is that I first tried to build it under 1.8. What I
> get is:
>
> $ rake
> (in /home/rubys/svn/libxml)
> rake aborted!
> No such file or directory - ext/xml/libxml.h
> /home/rubys/svn/libxml/Rakefile:18:in `read'
> (See full trace by running task with --trace)
>
> Did I miss a step?
I updated the Rakefile to shell out to the task/* scripts.
$ rake -T
(in /home/trans/Company/TigerOps/programs/libxml/trunk)
rake clean # Remove any temporary products.
rake clobber # Remove any generated file.
rake compile # Compile extensions.
rake default # Default task (compile, test and memory test)
rake memory # Run memory test suite.
rake rdoc # Generate rdoc documentation.
rake setup # Install to local site directory.
rake test # Run unit test suite.
T.
From hello at timperrett.com Thu Jan 31 09:00:36 2008
From: hello at timperrett.com (Tim Perrett)
Date: Thu, 31 Jan 2008 14:00:36 +0000
Subject: [libxml-devel] Compilling libxsl on OSX
Message-ID: <353B562B-9CEC-4C18-9B8F-8ECAE422CCCB@timperrett.com>
Hey guys,
Im trying to install the libxsl gem on OSX, but keep getting this error:
ldruby_xslt_transform_context.o:
symbolld(:s )symbol (nots )found notfor foundarchitecture forppc
architecture i386
collect2: collect2: ld returned 1 exit statusld returned 1 exit status
lipo: can't open input file: /var/folders/f1/f1tof6fRGDGh3f4-lir1i+++
+TI/-Tmp-//ccNVRFwL.out (No such file or directory)
make: *** [libxslt.bundle] Error 1
Any ideas how I can fix this?
Thanks
Tim
From rubys at intertwingly.net Thu Jan 31 10:13:23 2008
From: rubys at intertwingly.net (Sam Ruby)
Date: Thu, 31 Jan 2008 10:13:23 -0500
Subject: [libxml-devel] libxml2 on Ruby 1.9
In-Reply-To: <378860ba-408c-4434-9485-28c4f12c98cf@v4g2000hsf.googlegroups.com>
References: <479F7792.20406@intertwingly.net>
<378860ba-408c-4434-9485-28c4f12c98cf@v4g2000hsf.googlegroups.com>
Message-ID: <47A1E593.4030109@intertwingly.net>
Trans wrote:
>
> I updated the Rakefile to shell out to the task/* scripts.
Thanks!
With the attached patch, I've the following sequence works on Ruby 1.9,
revision 15360 (the latest HEAD):
rake clobber
rake compile
rake test
The patch should not be applies as is, as the rename of util.h to
ruby/util.h is a breaking change. Should be easy enough to handle in
extconf.rb.
My goal is to keep a watch on Ruby 19 and libxml2 to ensure that neither
commits any changes that breaks the other. More details can be found here:
http://intertwingly.net/blog/2008/01/31/Ruby-CI-Efforts
Let me know if you commit these changes, or how you want the extconf
changes to be handled, as once basic Ruby 1.9 support is in place, I
will add libxml to my list.
- Sam Ruby
From rubys at intertwingly.net Thu Jan 31 10:15:07 2008
From: rubys at intertwingly.net (Sam Ruby)
Date: Thu, 31 Jan 2008 10:15:07 -0500
Subject: [libxml-devel] libxml2 on Ruby 1.9
In-Reply-To: <47A1E593.4030109@intertwingly.net>
References: <479F7792.20406@intertwingly.net> <378860ba-408c-4434-9485-28c4f12c98cf@v4g2000hsf.googlegroups.com>
<47A1E593.4030109@intertwingly.net>
Message-ID: <47A1E5FB.90807@intertwingly.net>
Sam Ruby wrote:
> Trans wrote:
>> I updated the Rakefile to shell out to the task/* scripts.
>
> Thanks!
>
> With the attached patch, I've the following sequence works on Ruby 1.9,
> revision 15360 (the latest HEAD):
>
> rake clobber
> rake compile
> rake test
>
> The patch should not be applies as is, as the rename of util.h to
> ruby/util.h is a breaking change. Should be easy enough to handle in
> extconf.rb.
>
> My goal is to keep a watch on Ruby 19 and libxml2 to ensure that neither
> commits any changes that breaks the other. More details can be found here:
>
> http://intertwingly.net/blog/2008/01/31/Ruby-CI-Efforts
>
> Let me know if you commit these changes, or how you want the extconf
> changes to be handled, as once basic Ruby 1.9 support is in place, I
> will add libxml to my list.
>
> - Sam Ruby
Oops. This time, I'm going to include the patch. :-)
- Sam Ruby
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libxml.r19.patch
Type: text/x-patch
Size: 954 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/libxml-devel/attachments/20080131/434aec24/attachment.bin
From danj at 3skel.com Thu Jan 31 10:39:12 2008
From: danj at 3skel.com (Dan Janowski)
Date: Thu, 31 Jan 2008 10:39:12 -0500
Subject: [libxml-devel] libxml2 on Ruby 1.9
In-Reply-To: <47A1E5FB.90807@intertwingly.net>
References: <479F7792.20406@intertwingly.net> <378860ba-408c-4434-9485-28c4f12c98cf@v4g2000hsf.googlegroups.com>
<47A1E593.4030109@intertwingly.net>
<47A1E5FB.90807@intertwingly.net>
Message-ID: <1AE830AB-2974-4FE5-87A3-819E93E9A0B2@3skel.com>
Hi Sam,
Thank you for tracking these changes. In the interest of tracking all
changes so they may be properly applied, please submit this to the
patch tracker at this location:
http://rubyforge.org/tracker/?func=add&group_id=494&atid=1973
Dan
On Jan 31, 2008, at 10:15, Sam Ruby wrote:
> Sam Ruby wrote:
>> Trans wrote:
>>> I updated the Rakefile to shell out to the task/* scripts.
>> Thanks!
>> With the attached patch, I've the following sequence works on Ruby
>> 1.9, revision 15360 (the latest HEAD):
>> rake clobber
>> rake compile
>> rake test
>> The patch should not be applies as is, as the rename of util.h to
>> ruby/util.h is a breaking change. Should be easy enough to handle
>> in extconf.rb.
>> My goal is to keep a watch on Ruby 19 and libxml2 to ensure that
>> neither commits any changes that breaks the other. More details
>> can be found here:
>> http://intertwingly.net/blog/2008/01/31/Ruby-CI-Efforts
>> Let me know if you commit these changes, or how you want the
>> extconf changes to be handled, as once basic Ruby 1.9 support is in
>> place, I will add libxml to my list.
>> - Sam Ruby
>
> Oops. This time, I'm going to include the patch. :-)
>
> - Sam Ruby
> Index: ext/libxml/libxml.c
> ===================================================================
> --- ext/libxml/libxml.c (revision 256)
> +++ ext/libxml/libxml.c (working copy)
> @@ -4,9 +4,6 @@
>
> #include "libxml.h"
>
> -/* Ruby's util.h has ruby_strdup */
> -#include "util.h"
> -
> #ifdef xmlMalloc
> #undef xmlMalloc
> #endif
> Index: ext/libxml/libxml.h
> ===================================================================
> --- ext/libxml/libxml.h (revision 256)
> +++ ext/libxml/libxml.h (working copy)
> @@ -18,7 +18,7 @@
>
> #include
> #include
> -#include
> +#include
> #include
> #include
> #include
> @@ -35,6 +35,12 @@
> #define RSTRING_LEN(x) RSTRING(x)->len
> #endif
>
> +// not in Ruby 1.9
> +#ifndef GetWriteFile
> +#define GetWriteFile(fp) rb_io_stdio_file(fp)
> +#define OpenFile rb_io_t
> +#endif
> +
> #ifdef LIBXML_DEBUG_ENABLED
> #include
> #endif
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel
From rubys at intertwingly.net Thu Jan 31 10:46:05 2008
From: rubys at intertwingly.net (Sam Ruby)
Date: Thu, 31 Jan 2008 10:46:05 -0500
Subject: [libxml-devel] libxml2 on Ruby 1.9
In-Reply-To: <1AE830AB-2974-4FE5-87A3-819E93E9A0B2@3skel.com>
References: <479F7792.20406@intertwingly.net> <378860ba-408c-4434-9485-28c4f12c98cf@v4g2000hsf.googlegroups.com> <47A1E593.4030109@intertwingly.net> <47A1E5FB.90807@intertwingly.net>
<1AE830AB-2974-4FE5-87A3-819E93E9A0B2@3skel.com>
Message-ID: <47A1ED3D.1080405@intertwingly.net>
Dan Janowski wrote:
> Hi Sam,
>
> Thank you for tracking these changes. In the interest of tracking all
> changes so they may be properly applied, please submit this to the
> patch tracker at this location:
>
> http://rubyforge.org/tracker/?func=add&group_id=494&atid=1973
>
> Dan
Done:
http://rubyforge.org/tracker/index.php?func=detail&aid=17666&group_id=494&atid=1973
- Sam Ruby
From pat.eyler at gmail.com Thu Jan 31 10:51:27 2008
From: pat.eyler at gmail.com (pat eyler)
Date: Thu, 31 Jan 2008 08:51:27 -0700
Subject: [libxml-devel] libxml and Rubinius
Message-ID: <6fd0654b0801310751r4ca4b3f5se0ca1d89b01ca6da@mail.gmail.com>
has anyone done any work getting libxml to work on/with Rubinius?
--
thanks,
-pate
-------------------------
Duty makes us do things, Love make us do things well.
http://on-ruby.blogspot.com http://on-erlang.blogspot.com
http://on-soccer.blogspot.com
From danj at 3skel.com Thu Jan 31 11:09:36 2008
From: danj at 3skel.com (Dan Janowski)
Date: Thu, 31 Jan 2008 11:09:36 -0500
Subject: [libxml-devel] Project protocol
Message-ID: <9FB5DCE5-C5D7-415A-AAB8-3120F4273280@3skel.com>
My thanks to all of you for using, discussing, reporting and
contributing to the ruby-libxml extension. As more people become
involved and as the quantity of contributions and issues grows, it has
become more difficult to keep track of what needs to be done. With
this in mind, the following protocol is necessary for better execution:
Non-developer:
1. the libxml-devel mailing list is for support and discussion
2. Feature changes, bug reports, patches must be submitted to the
tracker at http://rubyforge.org/tracker/?group_id=494
Developer:
1. The trunk must always be in working order.
2. Narrow scoped bug fixes may be applied directly to the trunk.
3. Each developer should use a self named branch (i.e. danj-devel) for
making larger changes that may result in prolonged brokenness. The
developer should track the trunk and merge as required.
4. Larger branch based changes should be packaged into Release
Candidates using a change name and the SVN number for public
evaluation. i.e. xpath-1234 or build-1234.
5. Successful RC evaluation should result in a merge back to the
trunk, assignment of a release number, then publication.
I hope this will make it easier to apply consistent and productive
time slices for continuing work on the code base. If you find a
problem with anything said here or something omitted, please discuss.
Dan
From danj at 3skel.com Thu Jan 31 11:27:54 2008
From: danj at 3skel.com (Dan Janowski)
Date: Thu, 31 Jan 2008 11:27:54 -0500
Subject: [libxml-devel] libxml and Rubinius
In-Reply-To: <6fd0654b0801310751r4ca4b3f5se0ca1d89b01ca6da@mail.gmail.com>
References: <6fd0654b0801310751r4ca4b3f5se0ca1d89b01ca6da@mail.gmail.com>
Message-ID:
This entices me. The MRI internals (esp. the GC) are the biggest
obstacle to making this library work and I am beginning to really hate
them. I've even had this delusion that making this library work with
Subtend may enable effective repair of outstanding faults more easily
than trying to do it under MRI. Then I have this shimmering vision of
dumping the whole code base and just writing an FFI interface.
Dan
On Jan 31, 2008, at 10:51, pat eyler wrote:
> has anyone done any work getting libxml to work on/with Rubinius?
>
> --
> thanks,
> -pate
> -------------------------
> Duty makes us do things, Love make us do things well.
> http://on-ruby.blogspot.com http://on-erlang.blogspot.com
> http://on-soccer.blogspot.com
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel