From: "Richard W.M. Jones" <rjones@redhat.com>
To: cocci@inria.fr
Subject: [cocci] pcre vs pcre2
Date: Fri, 22 Jul 2022 20:23:27 +0100 [thread overview]
Message-ID: <20220722192327.GA28597@redhat.com> (raw)
PCRE (not PCRE2) is end of life: http://www.pcre.org/
and may be removed from Fedora:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/K3BUC6T5VIG7LXOV4RVFO7IUPE2LGA2J/
It seems as if coccinelle has an optional dep on PCRE enabled/disabled
through ./configure --enable-pcre-syntax. It's not entirely clear to
me what Fedora would lose by disabling this.
Does coccinelle plan to move to PCRE2?
I have moved a few projects over to PCRE2. It's definitely not an
automatic conversion, although it also wasn't especially difficult.
Here's libguestfs. This is mostly C and we maintain our own PCRE
bindings for OCaml which are not based on Markus Mottl's bindings, but
it should give you an idea of the changes:
https://github.com/libguestfs/libguestfs/commit/82493579f38f39769861f31403ccfb8e97b41f96
https://github.com/libguestfs/libguestfs-common/commit/0b244f2b0cfc920f2432f5df45e108583f0d2901
We decided not to support alternate PCRE or PCRE2 compiles since all
distros have provided PCRE2 for a long time.
Also:
https://github.com/mmottl/pcre-ocaml/issues/25
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit
next reply other threads:[~2022-07-22 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 19:23 Richard W.M. Jones [this message]
2022-07-22 19:30 ` [cocci] pcre vs pcre2 Julia Lawall
2022-09-20 13:46 ` Richard W.M. Jones
2022-07-23 5:38 ` Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220722192327.GA28597@redhat.com \
--to=rjones@redhat.com \
--cc=cocci@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).