On Jun 27, 11:18 am, Anurag Priyam wrote:
> > > If we want to leave rubyforge entirely, a google group needs to be setup.
> > > But it is very much prone to spam.
>
> > There already is a google group. We just need to detach it from the
> > old list-- no big deal.
>
> > http://groups.google.com
> > If we want to leave rubyforge entirely, a google group needs to be setup.
> > But it is very much prone to spam.
>
> There already is a google group. We just need to detach it from the
> old list-- no big deal.
>
> http://groups.google.com/group/libxml-devel
>
>
Trans, please can you elaborate
> Been out of the loop for a bit, but this is all about trying to get things
> set up so that the libxml crashing stuff can be investigated, right?
>
>
Kind of. We are moving libxml-ruby, libxslt-ruby and libxml4r ahead.
> When that particular issue with raising exceptions causing segfaults is
>
I think we should wait for Charlie's approval.
Go for it - sorry to delay things.
FYI, my githu name is cfis if you can add me in.
Charlie
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
On 6/26/2010 12:21 AM, Anurag Priyam wrote:
Well, I did setup a git repositories:
http://github.com/cfis/libxml-ruby
http://github.com/cfis/libxslt-ruby
You do not want to go with a maintainer libxml account then, as we
discussed before?
Oh sure if you want.
What changes
Tran,
> Btw, did anyone have a look at fastxml? Replicates libxml functionality
> with a Nokiogiri kind of interface. However there are a lot of projects that
> depend on libxml and I do not want any other project to take libxml's place.
> I will be devoting time from now on for libxml-ruby's dev
Tans,
On Sat, Jun 26, 2010 at 8:42 PM, Trans wrote:
>
>
> On Jun 26, 2:21 am, Anurag Priyam wrote:
> > > Well, I did setup a git repositories:
> >
> > >http://github.com/cfis/libxml-ruby
> > >http://github.com/cfis/libxslt-ruby
> >
> > You do not want to go with a maintainer libxml account then
Sure, but maybe very slight modifications might help :).
On Sat, Jun 26, 2010 at 8:43 PM, Trans wrote:
>
>
> On Jun 26, 2:23 am, Anurag Priyam wrote:
> > > To serve as a website for the projects Github pages can be setup.
> >
> > Once I have been added as a collaborator, I am doing this one fir
On Jun 26, 2:21 am, Anurag Priyam wrote:
> > Well, I did setup a git repositories:
>
> >http://github.com/cfis/libxml-ruby
> >http://github.com/cfis/libxslt-ruby
>
> You do not want to go with a maintainer libxml account then, as we discussed
> before?
>
> > What changes do I need to make?
>
> A
On Jun 26, 2:23 am, Anurag Priyam wrote:
> > To serve as a website for the projects Github pages can be setup.
>
> Once I have been added as a collaborator, I am doing this one first. They
> support Jekyll pages and I always wanted to give it a shot :).
Will you use the site we already have as
Been out of the loop for a bit, but this is all about trying to get things set
up so that the libxml crashing stuff can be investigated, right?
When that particular issue with raising exceptions causing segfaults is fixed,
I'd love to know about it. Will try and keep my eyes peeled, but nearly
>> Well, I did setup a git repositories:
>>
>>
>> http://github.com/cfis/libxml-ruby
>> http://github.com/cfis/libxslt-ruby
>>
>>
> You do not want to go with a maintainer libxml account then, as we
> discussed before?
>
>
I guess we are all waiting for Charlie's approval for the maintainer
accoun
Hi,
Libxml4r:
If you push up a clone of the libxml4r repo (and dont fork it), then
add me as a collaborator to that repo. I can delete mine and/or
re-fork it from the new account. This may be a little easier than
having Github support do it.
For libxml4r I can also put up some yard documentation
> To serve as a website for the projects Github pages can be setup.
>
>
Once I have been added as a collaborator, I am doing this one first. They
support Jekyll pages and I always wanted to give it a shot :).
--
Anurag Priyam,
2nd Year Undergraduate,
Department of Mechanical Engineering,
IIT Khar
>
>
> Well, I did setup a git repositories:
>
>
> http://github.com/cfis/libxml-ruby
> http://github.com/cfis/libxslt-ruby
>
>
You do not want to go with a maintainer libxml account then, as we discussed
before?
> What changes do I need to make?
>
>
Add collaborators. Those who wish to be one wi
Hi Anurag,
On 6/25/2010 1:48 AM, Anurag Priyam wrote:
Looks like Charlie is quite busy. I could act as a co-maintainer? As the
initial steps I will create the libxml account add collaborators and
clone the repositories.
Well, I did setup a git repositories:
http://github.com/cfis/libxml-ruby
On Jun 25, 3:48 am, Anurag Priyam wrote:
> Looks like Charlie is quite busy. I could act as a co-maintainer? As the
> initial steps I will create the libxml account add collaborators and clone
> the repositories.
>
> We can then start setting targets: porting completely to Ruby 1.9.2, fixing
> t
Looks like Charlie is quite busy. I could act as a co-maintainer? As the
initial steps I will create the libxml account add collaborators and clone
the repositories.
We can then start setting targets: porting completely to Ruby 1.9.2, fixing
the bugs, integrating patches and stuff. What say?
On W
On Wed, Jun 9, 2010 at 2:51 AM, Charlie Savage wrote:
>
> On 6/7/2010 11:23 PM, Anurag Priyam wrote:
>
>> I was thinking of creating a github account with the name libxml or
>> libxml-ruby. I have seen a few projects which do that. This way
>> switching maintainers can be easy. Github also has an
On Wed, Jun 9, 2010 at 3:14 AM, Dreamcat Four wrote:
> On Tue, Jun 8, 2010 at 10:21 PM, Charlie Savage wrote:
> > We could do that too. In that case, who owns the account? Aren't the
> issue
> > tracker/users attached to the project itself? Happy to add in everyone
> as
> > needed.
>
> The cu
On Jun 8, 6:39 pm, Dreamcat Four wrote:
> On Tue, Jun 8, 2010 at 11:03 PM, Trans wrote:
> > That setup really only makes sense if a project has multiple parts/
> > repos. At this point we have two libxml-ruby and libxmlr, and it's
> > possible libxmlr may merge into libxml-ruby. Are there other
On Tue, Jun 8, 2010 at 11:03 PM, Trans wrote:
> That setup really only makes sense if a project has multiple parts/
> repos. At this point we have two libxml-ruby and libxmlr, and it's
> possible libxmlr may merge into libxml-ruby. Are there other extension
> I don't know about that could find a h
On Jun 8, 2:23 am, Anurag Priyam wrote:
> I was thinking of creating a github account with the name libxml or
> libxml-ruby. I have seen a few projects which do that. This way switching
> maintainers can be easy. Github also has an issue tracker( have not used it
> ) and a wiki and a README can
On Tue, Jun 8, 2010 at 10:21 PM, Charlie Savage wrote:
> We could do that too. In that case, who owns the account? Aren't the issue
> tracker/users attached to the project itself? Happy to add in everyone as
> needed.
The currently nominated maintainer, which at the moment seems to be
you char
On 6/7/2010 11:23 PM, Anurag Priyam wrote:
I was thinking of creating a github account with the name libxml or
libxml-ruby. I have seen a few projects which do that. This way
switching maintainers can be easy. Github also has an issue tracker(
have not used it ) and a wiki and a README can be us
Well,
If you want to set that up for charles. That would be great. I think
you need to create a pool email address to give to the maintainer
(charlie), and to set up the account. Charlie and others could then
add their normal github accounts to that as "commiters".
For such an account its also wo
I was thinking of creating a github account with the name libxml or
libxml-ruby. I have seen a few projects which do that. This way switching
maintainers can be easy. Github also has an issue tracker( have not used it
) and a wiki and a README can be used for the contents on the RubyForge home
page
On 6/7/2010 2:43 AM, Trans wrote:
On Jun 7, 1:52 am, Charlie Savage wrote:
On 6/6/2010 11:22 AM, cthulhu wrote:
Maybe I could help, I'm pretty familiar with C. Besides, I use this
lib in production so I'm pretty interested in fixing those crashes.
Let me know when U'll push it to github.
Since I have access to libxml's RubyForge page, I will update it to
reflect the new github repository. This project
Done.
Great, thanks Anurag. Could you post a news item also mentioning the move?
Thanks,
Charlie
___
libxml-devel mailing l
On Jun 7, 1:52 am, Charlie Savage wrote:
> On 6/6/2010 11:22 AM, cthulhu wrote:
>
> > Maybe I could help, I'm pretty familiar with C. Besides, I use this
> > lib in production so I'm pretty interested in fixing those crashes.
> > Let me know when U'll push it to github.
>
> I mirrored the reposi
On 6/6/2010 11:22 AM, cthulhu wrote:
Maybe I could help, I'm pretty familiar with C. Besides, I use this
lib in production so I'm pretty interested in fixing those crashes.
Let me know when U'll push it to github.
I mirrored the repository from RubyForge a while back, its at
http://github.co
>
> Since I have access to libxml's RubyForge page, I will update it to
> reflect the new github repository. This project
>
Done.
--
Anurag Priyam,
2nd Year Undergraduate,
Department of Mechanical Engineering,
IIT Kharagpur.
+91-9775550642
___
libxml-d
Hello all,
Since I have access to libxml's RubyForge page, I will update it to reflect
the new github repository. This project would be a good chance for me to
learn Ruby's C API. I had planned to start hacking on libxml-ruby after I am
done with my Google Summer of Code project. It is a nice pro
Trans,
I moved it to Github a while back - its at
http://github.com/cfis/libxml-ruby.
Feel free to update RubyForge to note that if you'd like.
Charlie
On Jun 6, 10:17 am, cthulhu wrote:
Hi!
Is this project still alive? Is there github repository?
We do not currently have a main dev
On 6/6/2010 8:42 AM, Dreamcat Four wrote:
Hi,
This project has 0 active maintainers.
Most people use nokogiri these days.
Well, I casually do some maintenance. Happy if anyone else wants to
pitch in of course.
Charlie
Hi!
Is this project still alive? Is there github repository?
Maybe I could help, I'm pretty familiar with C. Besides, I use this
lib in production so I'm pretty interested in fixing those crashes.
Let me know when U'll push it to github.
On 6 Чер, 18:52, Trans wrote:
> On Jun 6, 10:17 am, cthulhu wrote:
>
> > Hi!
>
> > Is this project still alive? Is ther
On Jun 6, 10:17 am, cthulhu wrote:
> Hi!
>
> Is this project still alive? Is there github repository?
We do not currently have a main developer. I act as a sort of
custodian of the project, but I am not a C developer.
I have been thinking of moving the source to Github for some time.
Since you
Hi,
This project has 0 active maintainers.
Most people use nokogiri these days.
If you still want to use libxml-ruby, see the help and links on my homepage.
http://github.com/dreamcat4/libxml4r
On Sun, Jun 6, 2010 at 3:17 PM, cthulhu wrote:
> Hi!
>
> Is this project still alive? Is there githu
Hi!
Is this project still alive? Is there github repository?
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
The intersection is a null set. The best hope may be rubinius where the
extensions can be written in ruby. Fixing the memory model for nodes and
documents made a big difference, but the problems that are lingering are
elusive and compounded by ruby's obsficating GC. I put a lot of time into
it, but
I shifted out of libxml to the (much) slower REXML and an ad-hoc
over-the-network Java based XSD validation system. I would love to get
libxml-ruby working again. A lot of my projects will depend on it.
Dan, how can other people help? Is there someone who can coordinate
other people's efforts in
REXML is a mess, and not just because it's slower. Currently, the consensus
seems to be to use
Hpricot's XML mode until libxml stabilizes.
~~ Robert.
Saurabh Nanda wrote:
> I shifted out of libxml to the (much) slower REXML and an ad-hoc
> over-the-network Java based XSD validation system. I wo
I shifted out of libxml to the (much) slower REXML and an ad-hoc
over-the-network Java based XSD validation system. I would love to get
libxml-ruby working again. A lot of my projects will depend on it.
Dan, how can other people help? Is there someone who can coordinate
other people's efforts in t
I have been unable to continue work, my personal life not allowing. However,
the amount of effort that I have put into this has not cleared the library
of all its problems and it really needs active shared involvement of more
than just a single developer. This is sort of asking for manna, but the
n
I'm curious about the development status of libxml.
My application still core dumps fairly regularly though not in any way
that has proven useful for tracking down problems.
Is there any active development looking into the memory problems?
What is the status of libxml and libxsl for ruby 1.9?
Th
On Dec 4, 2007 12:20 AM, Paul Dlug <[EMAIL PROTECTED]> wrote:
>
> On Dec 3, 2007, at 5:09 PM, Dan Janowski wrote:
>
> > Paul,
> >
> > It looks fine at first glance, but I have not had time to apply the
> > patch and examine the results. The library is a lot less fragile than
> > when I got it, but
On Dec 3, 2007, at 5:09 PM, Dan Janowski wrote:
> Paul,
>
> It looks fine at first glance, but I have not had time to apply the
> patch and examine the results. The library is a lot less fragile than
> when I got it, but I need to be careful when adding code that is not
> fixing a bug to be sure
Paul,
It looks fine at first glance, but I have not had time to apply the
patch and examine the results. The library is a lot less fragile than
when I got it, but I need to be careful when adding code that is not
fixing a bug to be sure not to blow something else up.
Thanks for the patch. H
Dan,
Just wondering, any feedback on this?
Thanks,
Paul
On Nov 27, 2007, at 11:41 PM, Paul Dlug wrote:
>
> On Nov 27, 2007, at 3:26 PM, Dan Janowski wrote:
>
>> I see the merit in this kind of approach but it cannot conflict with
>> the libxml work flow. I.e.:
>>
>> instead of XML::Document.pa
On Nov 27, 2007, at 3:26 PM, Dan Janowski wrote:
I see the merit in this kind of approach but it cannot conflict with
the libxml work flow. I.e.:
instead of XML::Document.parse(xml) => Document
XML::Parser.parse(xml) => Document
If you want to update the patch for the current code base, I am
I see the merit in this kind of approach but it cannot conflict with
the libxml work flow. I.e.:
instead of XML::Document.parse(xml) => Document
XML::Parser.parse(xml) => Document
If you want to update the patch for the current code base, I am
willing to apply and eval it.
Dan
On Nov 27, 2
I see patch #7758 hasn't been worked on or updated since submission
(long ago):
http://rubyforge.org/tracker/index.php?func=detail&aid=7758&group_id=494&atid=1973
This seems like a great idea and the new parse method solves
eliminates the need for part of the patch I submitted (#15807). Is
52 matches
Mail list logo
