www/zoneminder, mysql vs mariadb

[Greg Troxel <gdt%lexort.com@localhost>]

I have prepared an update to 1.38.3 (from 1.36.37).

There's a fair bit of ick about bundled deps, which I've tried to deal
with but not really fix (filed upstream).

Mysql has become a more troubled ecosystem, as DBD::mysql has decided
that it's for mysql *only* and not for MariaDB.  There is DBD::MariaDB.
This breaks the basic flow that you need a msyql implementation, which
might be mysql or MariaDB.  pkgsrc's choices are

  Possible: 80 mariadb114 mariadb1011 mariadb106 mariadb105

with a default of mariadb114.  I take that as a clue that these days,
saying a package needs mysql mostly means that it needs MariaDB.

The problem with split DBD:: is that many packages that use mysql (the
interface) are not aware of this and are not set up to switch modules at
configure time and run time.

While I could make this work both ways, I propose a theory:

  Of the very small number of people who are using (up-to-date, from
  2026Q2) zoneminder from pkgsrc, zero of them are using it with
  mysql80.  And if it's a handful, they would like to migrate to mariadb
  and just haven't yet -- in which case them doing it sooner rather than
  later is a minor issue.

in which case I am inclined to just gc the accomodations for using
mysql80.  My impression is that these days Oracle mysql is disfavored
and fading.  I am increasingly leaning to minimize total effort across
the pkgsrc community, rather than spending effort to maintain packages
that would make things smoother for theoretical people that don't exist.

If you're using zoneminder, please speak up.  (Unlike technical comments
and help, I'm ok with getting a private note if you'd rather not admit
in public that you haven't switched to frigate yet -- I'll report just
an unattributed count here.)

Greg