On 11/09/2017 09:54 AM, p...@cpan.org wrote:
As those people or projects misuse some internals of perl we cannot
guarantee anything such that which may be broken or changed by updating
any module from cpan or external source not related to DBD::mysql.
Pali. This "argument" applies to a large portion of CPAN. All JSON
variants, various web frameworks, even things as mundane as math
libraries: https://rt.cpan.org/Public/Bug/Display.html?id=123268
As already stated more times, if there is some code which depends on
some internals, it should stay conserved in tested version as it can
break by updating anything (also unrelated). There is no other option
how to achieve that code stay working and does not corrupt something
else.
Pali, this is *not* how CPAN works. Nor is this even how /usr/bin/perl
works.
Maintaining such thing is something what I believe nobody wants. For
sure I'm not.
I will state several very obvious ( to me ) things, apologies if they
seem condescending: I simply do not know whether the participants on
this thread are talking about the same thing.
Pali's entire premise is flawed. In the grand scheme of things it makes
absolutely no difference what "maintainers want". Zero.
What the complaints in this thread are focused on is what the *users*
want. And every maintainer, Pali included, are irrevocably bound by the
general direction of wishes of the userbase.
The wishes are roughly ( and in order of inmportance ):
- Breakage is never silent and is rectified swiftly when reported ( and
is ideally never argued about )
- Upgrades are noneventful as a whole, and are as modular as possible (
i.e. a DBD upgrade does not drag in Test2 or something similarly
non-relevant )
- The overall library seems to move in a "better direction" ( more
performance, less memory use, support for newer protocols, etc )
Satisfy the above - and you do get the privilege of being a maintainer
of a central module with 15+ years of history.
If one can't - then the user-base is better off with the module
remaining "unmaintained" ( reusing Pali's terminology ), and Pali's
brave-new-world plan ending up in a different namespace. DBD::MariaDB is
an idea.
Cheers
