[Bug 280079] Move textproc/rasqal to pcre2
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 02 Jul 2024 04:24:40 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280079 Jason E. Hale <jhale@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC| |jhale@FreeBSD.org, | |office@FreeBSD.org Flags|maintainer-feedback?(kde@Fr |maintainer-feedback+ |eeBSD.org) | --- Comment #1 from Jason E. Hale <jhale@FreeBSD.org> --- (In reply to tjlegg from comment #0) In the current port, just changing the dependency in the Makefile is not the right thing to do as pcre2 won't be detected by the configure script and rasqal will fall back to using the POSIX regex library when built in a clean environment. All users would then have a needless dependency on pcre2 and those who build on live systems with pcre installed would have a missing dependency on pcre since it will be used if detected by default. IMO we have 3 options: 1. Update the port to the git version and use pcre2. 2. Remove the pcre dependency entirely and use POSIX regex. 3. Do nothing since pcre, while marked DEPRECATED, doesn't have an EXPIRATION_DATE set and has no known security vulnerabilities. The only consumers of rasqal are textproc/redland and textproc/redland-bindings. Nothing uses the bindings and the only current consumers of redland are editors/libreoffice and editors/openoffice-*. kde@ has historical reasons for maintaining rasqal and redland and we've just been holding on to them since there hasn't been much upstream activity over the years, but they would now probably be better off in the hands of office@. Not trying to pass the buck, but I'm just not that familiar with the office suites and what effects changing this port may have. Personally, I'm more in favor of option #2, but I'm CC'ing office@ to get their opinion and see if they want to take over maintainership of textproc/raptor2, textproc/rasqal, and textproc/redland* since they're irrelevant to KDE these days and only relevant to office@-maintained ports. -- You are receiving this mail because: You are on the CC list for the bug.