Comment 11 for bug 448285

OK - here's my take on how lxml (and likewise numpy) is handled on the three arches as of right now:

linux: No check at build time. If the packager (of the binary) adds a dep/recommend, python-lxml is installed when inkscape is installed. If not, then the extensions themselves complain about missing python-lxml

win32: Simply an egg included in the bundled Python (2.5). Can find no reference to this in SVN, or any sort of automated set-up within the win32 source 7zip.

OS X: Many versions copied over at build time: see line 280 of inkcape/packaging/macosx/osx-app.sh

I'm a little unclear on where the win32 version comes from - but I do not have much experience at building on Windows. AFAICT, there must be another step between SVN and the Win32 source.