-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to pcre2 #366
Comments
Cropi
added a commit
to Cropi/liblognorm
that referenced
this issue
Jun 6, 2023
Fixes rsyslog#366 Upstream stopped the support for the old 'pcre' package. See https://www.pcre.org/ It only supports the new 'pcre2' version, we should replace the current pcre with the newer pcre2.
Cropi
added a commit
to Cropi/liblognorm
that referenced
this issue
Jun 6, 2023
Fixes rsyslog#366 Upstream stopped the support for the old 'pcre' package. See https://www.pcre.org/ It only supports the new 'pcre2' version, we should replace the current pcre with the newer pcre2.
Cropi
added a commit
to Cropi/liblognorm
that referenced
this issue
Jun 6, 2023
Fixes rsyslog#366 Upstream stopped the support for the old 'pcre' package. See https://www.pcre.org/ It only supports the new 'pcre2' version, we should replace the current pcre with the newer pcre2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As from the pcre-8.45, the upstream stopped supporting the old pcre [1] package. The recommended procedure is to switch onto the new pcre2 library that has full upstream support. Pcre2 has been released ~7 years ago [2] but it's not fully compatible with pcre, so some code changes are expected. What do you think?
[1] https://www.pcre.org/
[2] https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html
The text was updated successfully, but these errors were encountered: