Re: PCRE v2 compile error, was Re: What's cooking in git.git (May 2017, #01; Mon, 1)

From: Junio C Hamano <gitster@pobox.com>
Date: May 8, 2017, 07:10 UTC
Message-ID: <xmqqpofj7rim.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CACBZZX75nvfQft-gjUG+YP0Y-e-=Knm3bMeDWHSUF=Juz9Ua5Q@mail.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

Show 6 quoted lines

> This won't be in my next PCRE submission, but I have a path locally to
> simply import PCRE into git.git as compat/pcre2, so it can be compiled
> with NO_PCRE=Y similar to how NO_REGEX=Y works.
>
> This will hopefully address your concerns partially, i.e. when you do
> want to try it out it'll be easier.

Eek, please don't.

Until pcre2 becomes _so_ stable that all reasonable distros give choice to the end-users to install it easily in a packaged form, such a "not a fork, but a copy" will be a moving target that I'd rather not to have in compat/. IOW, our compat/$pkg should be a last resort to help those on distros that are so hard to convince to carry the version/variant of $pkg we would like to use.