On Fri, Jul 8, 2011 at 9:09 AM, Larry Gritz <[email protected]> wrote: > Most of the code in libutil is ours. pugixml is the exception -- it's so > small, we incorporated the code rather than add an external dependency. It > is slightly modified in order to put it in our namespace -- I'm not sure if > that makes it ok in Fedora's book. If that's a problem, I'm sure we could > easily make a cmake option that would pull in an external pugixml rather than > use the embedded one (which you can enable for the Fedora builds).
A cmake option would be great. It should be fairly trivial for me to package it I've already downloaded the source from their website. > What is the nature of the Fedora rule about libraries? Does it only apply to > other Fedora libraries? Or any code we've incorporated from elsewhere? For > example, src/dpx.imageio incorporates a project libdpx, but that's very > obscure and not a reasonable external dependency for Fedora. I'm not sure I can explain it fully but there are several reasons. One is bloat, while not a big deal in this particular case, you can see that if everyone statically copied in common libraries that it would make a lot of packages bigger. Second is traceability/ownership reasons. When something breaks in a library, who does the bug get reported to? The package/project that's using it, or the library itself? Here's the full explanation: http://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries Sounds like I need to make a pugixml package. Assuming I don't run into any major building issues I should have something by this weekend. Thanks, Richard _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
