Issue 93297 - No way to specify external xmlsec
Summary: No way to specify external xmlsec
Status: UNCONFIRMED
Alias: None
Product: xml
Classification: Code
Component: code (show other issues)
Version: DEV300m29
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-31 17:26 UTC by panbk
Modified: 2013-01-29 21:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description panbk 2008-08-31 17:26:00 UTC 
On FreeBSD, at least, there exists a port of xmlsec
(http://freshports.org/security/xmlsec1). Other systems, likely, also provide
the library already. However, telling OOo build to use that instead of the
version bundled with OOo is not currently possible.
Comment 1 Mathias_Bauer 2008-09-01 12:16:22 UTC 
As no patch is attached I assume that the type should be "DEFECT".
Jochen, perhaps this is one for you.
Comment 2 joachim.lingner 2008-09-01 14:46:08 UTC 
Please find someone who provides a patch for this. 

You should also be aware that the xmlsec library in the OOo environment contains
a couple of patches, which may not be contained in other versions. Also the
newer versions of libxmlsec may not work with OOo. Therefore you should not rely
on OOo working correctly with the system's xmlsec library.