Having libxml2 available during the build process is not a problem IMO
It's looking like zanshin and Sharing.py are the "culprits" :) On Jan 27, 2006, at 1:04 PM, Robin Dunn wrote:
Heikki Toivonen wrote:libxml2 yesAndi pointed out that we might be able to replace this with something else (possibly smaller even), which could also get rid of the patch requirement. I know zanshin uses libxml2 currently. Anything else?The wxPython build process currently uses libxml2 for parsing the SWIG xml output and generating a set of %rename directives.-- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
--- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
