Bug 269115 - databases/postgresql13-server: request to enable XML option by default or define a flavor
Summary: databases/postgresql13-server: request to enable XML option by default or def...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Palle Girgensohn
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-23 12:41 UTC by topical
Modified: 2023-07-29 06:22 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description topical 2023-01-23 12:41:06 UTC
I have some servers that require XML support of postgresql server.

In theory, I can just build postgresql myself, enabling the XML option. 

In practise, compiling postgresql server implies building llvm. But: building llvm is no fun - it is big and consumes lots of memory and cpu cycles.

In the end, my adopted package takes just 40 KByte (!) more disk space. 

Could the maintainer please consider adding XML by default or, if there are reasons to not do so, add a flavour? This would be great.

Thank you a lot for considering this.
Comment 1 dereckson 2023-05-25 04:24:48 UTC
Orbeon Forms requires this too.
Comment 2 Palle Girgensohn freebsd_committer freebsd_triage 2023-07-05 14:23:45 UTC
So, best way would be to add XML ON as default, and possibly add flavour for noxml?

The original rationale around removing XML from the default build was that the xml packages had bad reputation for security flaws. This is always the case with XML, I guess, but I don't think it actually motivates not linking the library. You most oftenly actually need to USE the xml features to expose yourself to any security problems.
Comment 3 dereckson 2023-07-06 13:56:52 UTC
I'd also like to add LLVM is moving to include libxml support.

On a machine, I had already libxml installed, through a llvm package (not the base system).

So that could become standard.

And yes, there are still XML security issues, including for libxml:

https://www.cvedetails.com/vulnerability-list/vendor_id-1962/product_id-3311/Xmlsoft-Libxml2.html