From rosco at roscopeco.co.uk  Sat Jan  6 07:00:24 2007
From: rosco at roscopeco.co.uk (Ross Bamford)
Date: Sat, 06 Jan 2007 12:00:24 -0000
Subject: [libxml-devel] Bug Day
Message-ID: <op.tlqeayxckc9f7k@localhost.localdomain>

Hi,

Okay, here's a little more on the upcoming bug day. This is all just my  
thoughts, it'd be great to get any input on this at all.

When
====
I think we should hold the bug day in February, maybe around the 10-15th.  
Pat recommends we announce at four weeks before, two weeks before, and a  
week before, so that's what we should do.

Activities
==========
There've been a few bugs over the past week, a couple that are probably a  
bit in-depth for a bug day, but at least one concerns poor test coverage.  
We should make a start on getting as many (valid ;)) bugs into the  
trackers as possible. I'm planning to comb through the tests and find weak  
spots in coverage, which I'll then file bugs against.

As well as test coverage, we could also file bugs against documentation  
(much of what's there is cursory, to say the least), and bad code that's  
knocking around in there.

How
===
I think that, on the day, developers should be available on the list and  
in an IRC channel somewhere, to help get people started and discuss  
possible patches, etc. I'm happy to do this, of course - if anyone else  
might be able to pitch in with that it'd be great.

Basically, people who want to get involved on the day will pick an issue,  
maybe discuss a possible fix with us, and then send up a patch when  
they're ready. We'd then check the patches, and commit them to CVS as  
appropriate, or discuss them further with the submitter. Does anyone feel  
like taking care of that side of things?

That's it. As I say, any thoughts much appreciated.

Cheers,
-- 
Ross Bamford - rosco at roscopeco.co.uk

From pat.eyler at gmail.com  Sat Jan  6 11:02:54 2007
From: pat.eyler at gmail.com (pat eyler)
Date: Sat, 6 Jan 2007 09:02:54 -0700
Subject: [libxml-devel] Bug Day
In-Reply-To: <op.tlqeayxckc9f7k@localhost.localdomain>
References: <op.tlqeayxckc9f7k@localhost.localdomain>
Message-ID: <6fd0654b0701060802y5c5e2d94n13e42592820b0f2f@mail.gmail.com>

On 1/6/07, Ross Bamford <rosco at roscopeco.co.uk> wrote:
> Hi,
>
> Okay, here's a little more on the upcoming bug day. This is all just my
> thoughts, it'd be great to get any input on this at all.
>
> When
> ====
> I think we should hold the bug day in February, maybe around the 10-15th.
> Pat recommends we announce at four weeks before, two weeks before, and a
> week before, so that's what we should do.

I'm giving advice, not commandments.  Please make sure that whatever
you do is right for the project.

>
> Activities
> ==========
> There've been a few bugs over the past week, a couple that are probably a
> bit in-depth for a bug day, but at least one concerns poor test coverage.
> We should make a start on getting as many (valid ;)) bugs into the
> trackers as possible. I'm planning to comb through the tests and find weak
> spots in coverage, which I'll then file bugs against.

Which tools are you using?  If you can find a way to do it, valgrind might
be a good thing to add to your toolkit.

>
> As well as test coverage, we could also file bugs against documentation
> (much of what's there is cursory, to say the least), and bad code that's
> knocking around in there.
>

If the rubinius guys can get RNI done in time, getting libxml working on
rubinius would be a fun project for a bug day too.

> How
> ===
> I think that, on the day, developers should be available on the list and
> in an IRC channel somewhere, to help get people started and discuss
> possible patches, etc. I'm happy to do this, of course - if anyone else
> might be able to pitch in with that it'd be great.
>

I'd be happy to do what I can (mostly advertising and cheerleading).


> Basically, people who want to get involved on the day will pick an issue,
> maybe discuss a possible fix with us, and then send up a patch when
> they're ready. We'd then check the patches, and commit them to CVS as
> appropriate, or discuss them further with the submitter. Does anyone feel
> like taking care of that side of things?
>
> That's it. As I say, any thoughts much appreciated.
>
> Cheers,
> --
> Ross Bamford - rosco at roscopeco.co.uk
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel
>


-- 
thanks,
-pate
-------------------------
http://on-ruby.blogspot.com

From rosco at roscopeco.co.uk  Thu Jan 11 04:59:29 2007
From: rosco at roscopeco.co.uk (Ross Bamford)
Date: Thu, 11 Jan 2007 09:59:29 -0000
Subject: [libxml-devel] Bug Day
In-Reply-To: <6fd0654b0701060802y5c5e2d94n13e42592820b0f2f@mail.gmail.com>
References: <op.tlqeayxckc9f7k@localhost.localdomain>
	<6fd0654b0701060802y5c5e2d94n13e42592820b0f2f@mail.gmail.com>
Message-ID: <op.tlzh1fjekc9f7k@localhost.localdomain>

On Sat, 06 Jan 2007 16:02:54 -0000, pat eyler <pat.eyler at gmail.com> wrote:

> On 1/6/07, Ross Bamford <rosco at roscopeco.co.uk> wrote:
>> Hi,
>>
>> Okay, here's a little more on the upcoming bug day. This is all just my
>> thoughts, it'd be great to get any input on this at all.
>>
>> When
>> ====
>> I think we should hold the bug day in February, maybe around the  
>> 10-15th.
>> Pat recommends we announce at four weeks before, two weeks before, and a
>> week before, so that's what we should do.
>
> I'm giving advice, not commandments.  Please make sure that whatever
> you do is right for the project.
>

Sorry, that came out wrong - I meant "So that's what _I think_ we should  
do". Really I was hoping to spark some debate...

>>
>> Activities
>> ==========
>> There've been a few bugs over the past week, a couple that are probably  
>> a
>> bit in-depth for a bug day, but at least one concerns poor test  
>> coverage.
>> We should make a start on getting as many (valid ;)) bugs into the
>> trackers as possible. I'm planning to comb through the tests and find  
>> weak
>> spots in coverage, which I'll then file bugs against.
>
> Which tools are you using?  If you can find a way to do it, valgrind  
> might
> be a good thing to add to your toolkit.
>

Don't worry, Sean introduced me to Valgrind shortly after I joined the  
project, but right now it's not helping all that much: the main leak we  
still have concerns interaction between libxml2's memory management, and  
the binding, in that I obviously don't understand the former properly and  
so the latter is leaking a bit (rather than segfaulting) :( But I'm  
working on it, as best I can. I know it leaks, and I know where from  
(primarily, nodes copied out of a document), I just don't (yet) know how  
to fix it, while keeping libxml2 happy.

>>
>> As well as test coverage, we could also file bugs against documentation
>> (much of what's there is cursory, to say the least), and bad code that's
>> knocking around in there.
>>
>
> If the rubinius guys can get RNI done in time, getting libxml working on
> rubinius would be a fun project for a bug day too.
>

Hmm, interesting. There's also a bit of work done for ruby 1.9  
compatibility. I'll file a bug.

>> How
>> ===
>> I think that, on the day, developers should be available on the list and
>> in an IRC channel somewhere, to help get people started and discuss
>> possible patches, etc. I'm happy to do this, of course - if anyone else
>> might be able to pitch in with that it'd be great.
>>
>
> I'd be happy to do what I can (mostly advertising and cheerleading).
>

Very cool, thanks Pat :).

Cheers,
-- 
Ross Bamford - rosco at roscopeco.co.uk

From keith at oreilly.com  Sun Jan 14 15:05:51 2007
From: keith at oreilly.com (Keith Fahlgren)
Date: Sun, 14 Jan 2007 12:05:51 -0800
Subject: [libxml-devel] doc.find and Namespace confusion
Message-ID: <45AA8D1F.1010101@oreilly.com>

Hey,


I'm curious what I'm doing wrong in the IRB session below. I'd expect that:
   n = doc.find("*").to_a.first
   # not literal ==, just equivalent
   doc.find(n.path).to_a.first == n

Is that not supposed to be true?


Thanks,
Keith


# for the record:
/opt/local/lib/ruby/gems/1.8/gems/libxml-ruby-0.3.8.2/lib keith2$ ruby 
../tests/libxml_test.rb
VERSION: 0.3.8.2

# irb session:
$ irb --prompt xmp libxml.irb
require 'rubygems'
# => true
require 'xml/libxml'
# => true
doc = XML::Parser.string(<<EOFEED
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" 
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" 
xmlns:dc="http://purl.org/dc/elements/1.1/">
   <title>Books</title>
   <link rel="first" href="https://dummy.com/atom/oreilly/books" />
   <link rel="last" href="https://dummy.com/atom/oreilly/books?page=51" />
   <link rel="next" href="https://dummy.com/atom/oreilly/books?page=2" />
   <subtitle>Stores O'Reilly Book Content</subtitle>
   <entry>
     <title>Dummy Book</title>

     <link rel="edit" href="https://dummy.com/atom/oreilly/books/172049" />
     <link rel="edit-media" 
href="https://dummy.com/source/oreilly/books/172049" />
     <author />
     <id>tag:oreilly.com,2007:172049</id>
     <updated>2007-01-13T00:25:07Z</updated>
     <published>2007-01-13T00:25:07Z</published>
     <content type="application/docbook+xml" 
src="https://dummy.com/source/oreilly/books/172049" />

     <summary type="text" />
   </entry>
</feed>
EOFEED
).parse; nil
# => nil
doc.class
# => XML::Document
n1 = doc.find("*").to_a.first
# => <title>Books</title>
n1.path
# => "/feed/title"
n2 = doc.find(n1.path).to_a.first  # huh?
# => nil
n2 # bah!
# => nil
namespace = "http://www.w3.org/2005/Atom"
# => "http://www.w3.org/2005/Atom"
doc.find("*", namespace).each {|node|
   puts "PATH " + node.path; puts "CONTENT " + node.content[0..10]
   doc.find(node.path, namespace).each {|alt_node|
     # this'll never be run
     puts "REAL_PATH " + alt_node.path; puts "REAL CONTENT " + 
alt_node.content[0..10]
   }
}
PATH /feed/title
CONTENT Books
PATH /feed/link[1]
CONTENT
PATH /feed/link[2]
CONTENT
PATH /feed/link[3]
CONTENT
PATH /feed/subtitle
CONTENT Stores O'Re
PATH /feed/entry
CONTENT
     Dummy
# => <title>Books</title><link rel="first" 
href="https://dummy.com/atom/oreilly/books"/><link rel="last" 
href="https://dummy.com/atom/oreilly/books?page=51"/><link rel="next" 
href="https://dummy.com/atom/oreilly/books?page=2"/><subtitle>Stores 
O'Reilly Book Content</subtitle><entry>
     <title>Dummy Book</title>

     <link rel="edit" href="https://dummy.com/atom/oreilly/books/172049"/>
     <link rel="edit-media" 
href="https://dummy.com/source/oreilly/books/172049"/>
     <author/>
     <id>tag:oreilly.com,2007:172049</id>
     <updated>2007-01-13T00:25:07Z</updated>
     <published>2007-01-13T00:25:07Z</published>
     <content type="application/docbook+xml" 
src="https://dummy.com/source/oreilly/books/172049"/>

     <summary type="text"/>
   </entry>



or here: http://kfahlgren.com/code/libxml.irb





From dracognizer at gmail.com  Wed Jan 24 13:16:55 2007
From: dracognizer at gmail.com (Thibault Martin-Lagardette)
Date: Wed, 24 Jan 2007 19:16:55 +0100
Subject: [libxml-devel] Problems using libxml installed with gems on Ubuntu
	6.10
Message-ID: <b9f759f50701241016x72f41793m69e491fd475163d5@mail.gmail.com>

Hello all.

As a PHP developer, I recently decided to get to know ruby, and
wanted, as a beginning, to create a small ruby gmail client, like the
python one.

Working under Ubuntu 6.10, I installed ruby 1.8 via apt-get, and then
RubyGems myself.

After beeing able to retrieve the XML atom feed from Gmail, I wanted
to parse the XML file.
I didn't want to use Rexml when I saw its performances.
Thus I installed libxml-ruby via the command: "gem install -r libxml-ruby".

And now that I want to use it, here's what I get:

-- Snippet --
/usr/lib/ruby/gems/1.8/gems/libxml-ruby-0.3.8.4/lib/xml/libxml.rb:5:
uninitialized constant XML
(NameError)
        from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
`require'
        from ./gmail-atom.rb:6
-- End Snippet --

Here's my little bit of code :

-- Snippet --
#!/usr/bin/ruby

require 'rubygems'
require 'open-uri'
require 'xml/libxml_so' # I tried w/ and w/o it...
require 'xml/libxml'

open("https://mail.google.com/mail/feed/atom",
         :http_basic_authentication => ['login', 'passwd']
        ) do |content|
  feed = content.read
  xmlfeed = XML::Parser.string(feed).parse
  xmlroot = xmlfeed.root
  p xmlroot.class
  p xmlroot.methods.sort
end
-- End Snippet --


The matter is that xml/libxml doesn't seem to load libxml_so.so which
is where the XML module is defined...
Downloading the gem, or the source and building it myself does the same thing.
And oh, I tried installing libxml via apt-get, buth it's the 3.4
version, and without, for instance, the "each" or "first_child"
methods...

Any idea?

Thanks a lot in advance!

-- 
Thibault Martin-Lagardette.