Re: libneon version in FC5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2006-01-19 at 13:06 +0000, Joe Orton wrote:
> On Wed, Jan 18, 2006 at 05:14:52PM +0100, Christian Fredrik Kalager Schaller wrote:
> > Any chance to have FC5 use the 0.25.x releases of neon instead of
> > 0.24.x?  The reason is that there are a relatively critical fix for
> > GStreamer usage of libneon coming in the upcoming  0.25.5 release.
> > While the 0.25.5 release might not make it out before FC5 freezes, 
> > at least using 0.25.4 would make the migration painless, while upgrading
> > from 0.24.x to 0.25.x is very pain full (mainly due to OpenOffice using
> > it).
> 
> Yeah, really the question is "can someone upgrade OpenOffice to support 
> the neon 0.25.x API".  I had a brief look at it, but my C++ knowledge 
> is... lacking.  There are only a couple of places which need to be 
> changed, though.

I took a look a while ago when this first came up, but I'm totally
unfamiliar with neon, and the old api didn't appear to have a trivial
mapping to the new api.

If there was either an upgrade route from the old neon api to the new
neon api documented somewhere, or a sample substantive program that
successfully moved from old to new api to use as a reference change then
I could probably whack out the needed changes. 

The OOo neon using source is in ucb/source/ucp/webdav

and grep -r ne_ shows....

./UCBDeadPropertyValue.cxx:#include <neon/ne_xml.h>
./UCBDeadPropertyValue.cxx:    ne_xml_parser * parser = ne_xml_create();
./UCBDeadPropertyValue.cxx:        ne_xml_push_handler( parser,
./UCBDeadPropertyValue.cxx:        ne_xml_parse( parser,
rInData.getStr(), rInData.getLength() );
./UCBDeadPropertyValue.cxx:        success = !!ne_xml_valid( parser );
./UCBDeadPropertyValue.cxx:        ne_xml_destroy( parser );
./LockEntrySequence.cxx:#include <neon/ne_xml.h>
./LockEntrySequence.cxx:        ne_xml_parser * parser =
ne_xml_create();
./LockEntrySequence.cxx:        ne_xml_push_handler( parser,
./LockEntrySequence.cxx:        ne_xml_parse( parser,
./LockEntrySequence.cxx:        success = !!ne_xml_valid( parser );
./LockEntrySequence.cxx:        ne_xml_destroy( parser );
./LinkSequence.cxx:#include <neon/ne_xml.h>
./LinkSequence.cxx:        ne_xml_parser * parser = ne_xml_create();
./LinkSequence.cxx:        ne_xml_push_handler( parser,
./LinkSequence.cxx:        ne_xml_parse( parser,
./LinkSequence.cxx:        success = !!ne_xml_valid( parser );
./LinkSequence.cxx:        ne_xml_destroy( parser );
./LockSequence.cxx:#include <neon/ne_xml.h>
./LockSequence.cxx:        ne_xml_parser * parser = ne_xml_create();
./LockSequence.cxx:        ne_xml_push_handler( parser,
./LockSequence.cxx:        ne_xml_parse( parser,
./LockSequence.cxx:        success = !!ne_xml_valid( parser );
./LockSequence.cxx:        ne_xml_destroy( parser );

C.

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux