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

From: Duy Nguyen <pclouds@gmail.com>
Date: May 3, 2017, 11:15 UTC
Message-ID: <CACsJy8C1vaNFint17-ASy=RQnQswEJf-goQ-wiRCFdkeh+punw@mail.gmail.com>
In-Reply-To: <alpine.DEB.2.20.1705031139090.3480@virtualbox>

On Wed, May 3, 2017 at 4:45 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

>>     So it makes sense to give our downstream distributors a nudge to
>>     switch over to it.

Some contributor (i.e. me) was not happy with this nudging though. The other day I switched to some branch (probably 'pu') and the build failed because, guess what, I didn't have pcre2 installed. If I set USE_LIBPCRE1 then I lose pcre support when switching to other branches. And no, I don't want to install libpcre2, not when I'm forced to this way.

188 packages on Gentoo optionally depend on libpcre, 6 packages on libpcre2. Chances that a Gentoo user has libpcre2 already are rather low. I'll revisit my installation when the level of libpcre2 support grows a bit more than that. You can nudge distributors directly, probably more efficient too.

Show 6 quoted lines

> ...
>
> I hate to be that someone, but it has to be said: this is a disruptive
> change, and it would be a lot better to make it an opt-in at first, and
> when the dust settled about this option and many distributions have opted
> in already because of the benefits and tested this thoroughly in practice,

Agreed.

-- 
Duy