zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: Zsh workers <zsh-workers@zsh.org>
Subject: Re: PATCH: migrate pcre module to pcre2
Date: Wed, 24 May 2023 20:11:57 +0200	[thread overview]
Message-ID: <95739-1684951917.792064@3-Qz.UjNX.7X1-> (raw)
In-Reply-To: <ZF7H9wmSFQ1l19xG@fullerene.field.pennock-tech.net>

On 12 May, Phil Pennock wrote:
> I handed in my commit bit a while back because I used it so rarely and
> it felt better for commit to be only the people more actively involved.
> Shells and their provenance matter.  So I can't commit.

If I remember correctly, you indicated at the time that it shouldn't be
committed, at least not at that time. We probably have more of a problem
with patches getting missed than having to be backed out later. Trust
and competence don't expire if not used.

> My main motivation with RE2 was to get to something which all vendors
> will actually include when distributing.  The reason can't be licensing,
> since the PCRE lib is BSD licensed.

Do Apple include any of pcre, pcre2 and re2 already with macOS? It's
difficult to guess at their motivations. Zsh's build system linking pcre
into every ELF file by default if you enable pcre may not help. They
must have put some thought into at least their initial packaging of zsh
as they stripped out some of the shell functions.

> I'd seen RE2 pick up quite a bit of steam and wanted to explore to see
> how feasible it was.
>
> Ideally, we'd have a contact within Apple who can tell us what they
> might or might not consider, so that we can have working regexps with
> semantics younger than POSIX.2 (1992) and some more actual utility.  I'm

The one time I had a chance to speak to an actual Apple employee, and
that was someone far removed from the Unix layer, they only reinforced
my general impression that Apple really don't care about the shell and
Unix part of macOS in general. The change of default shell was likely
due to licencing alone. Did Apple at least provide 5.8.1 as a security
patch? RHEL 8 still comes with a vulnerable 5.8 so it would seem that
us doing security only releases is a waste of time.

I generally stick with zsh pattern matching out of habit. =~ seems to be
a popular feature, though, I guess people know and understand regexes.
Does bash ignore the system regex library and use the GNU one on all
systems? That's equivalent to us pulling something like TRE or PCRE into
the zsh source tree and forcing its use.

Oliver


  reply	other threads:[~2023-05-24 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 23:35 Oliver Kiddle
2023-05-06  4:44 ` named capture groups with PCRE matching (Was: PATCH: migrate pcre module to pcre2) Stephane Chazelas
2023-05-06 18:56   ` Bart Schaefer
2023-05-06 23:06     ` Oliver Kiddle
2023-05-10 23:26 ` PATCH: migrate pcre module to pcre2 Oliver Kiddle
2023-05-12 23:12 ` Phil Pennock
2023-05-24 18:11   ` Oliver Kiddle [this message]
2023-06-13  7:35 ` Jun T
2023-06-19  8:20   ` Jun T

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=95739-1684951917.792064@3-Qz.UjNX.7X1- \
    --to=opk@zsh.org \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).