GNOME Bugzilla – Bug 332290
Using system libneon
Last modified: 2008-12-21 20:22:43 UTC
I have noticed that the http module includes the whole libneon sources and links statically to them. However, when libneon is available on the system, it would be much better to use the system version and link dynamically to it. I can work on that by myself and provide a patch if you don't feel it is important, but first, I'd like to know if this is feasible at all, or if gnome-vfs always requires a specific version, or if there are other good reasons to link statically to neon.
The problem is that we exchange the whole IO layer of neon to use the gnme-vfs io functions, i.e. Socket Buffer, resolver, ssl, etc, and we also have some customizations to neon regarding http streaming ... this and the fact that neon isnt API stable and we have to port the while method to new api version make this probably a WONTFIX for the next time. Sorry but thanks for taking the time to file the bug and also thanks for the offer to make the patch ... :) Cheers, Christian
Created attachment 125110 [details] [review] Use system libneon In case opinions on this have changed in the meanwhile, especially given that gnome-vfs is effectively deprecated (but still significantly used) and that bugs like bug 531442 are cropping up (which is fixed in upstream neon, but not in gnome-vfs' ancient version), here's a patch against current SVN head to use the system libneon. It may not be as efficient, but on the plus side it's up to 4 years newer than the 2004 snapshot in gnome-vfs....