On 11/09/2017 01:46 PM, Noel Butler wrote:
On 09/11/2017 21:32, p...@cpan.org wrote:
What the complaints in this thread are focused on is what the *users*
want.
and the users want now, or will need in the near future, to build with
latest, stable and recommended versions of MariaDB and MySQL.
Which is a great thing to want. I want this too. This is not what the
thread is about.
The problem stems from Pali mashing together 3(!)* independent concerns,
and presenting them as an "all or nothing" proposition:
1. Inability to build against latest libmysql libs
2. Several security fixes
3. Entirely redefining how unicode is handled throughout the stack
If the ( artificial ) choice is the-above-3-together-or-nothing, then
the logical answer is "of course we rather have nothing until someone
else comes by and fixes 1 and 2, leaving 3 alone"
If Pali is willing to *permanently* back off from changing anything
related to 3 ( regardless how displeasing it is ) - then this becomes a
completely different conversation.
Not even a hint of such willingness has been demonstrated. This is what
is being discussed.
Cheers
* There are actual 4 issues: there is also intentional breakage of
bigint handling within the driver, which already shipped to CPAN at the
start of 2017 and still has not been backed out, despite multiple pleas,
including at least one large Perl shop declaring that DBD::mysql is
unusable to them as it stands right now:
https://github.com/perl5-dbi/DBD-mysql/pull/74
