All,
I took over maintainership of p5-DBD-mysql last week. Apparently I
unwittingly managed to poke a hornets nest. Upstream author changed the
code to make it only compatible with MySQL 8.x. I've tried patching out
some of those changes but it requires quite an effort and is, in the end,
unmainta
There is a third option.
Create both p5-DBD-mysql4 and p5-DBD-mysql5 using the respective versions, and
turn p5-DBD-mysql into a meta-port that uses DEFAULT_VERSIONS to select one of
the two numbered ports. There is precedent for this in the current ports tree,
but I can’t comment on how well i
Hi Remko,
It seems that the situation may be even more complicated than you describe.
Upstream of DBD-mariadb lately made some unfriendly steps which in
certain conditions may cause conflicts (up to crashes) with MariaDB server.
It is the reason why DBD-mysql has been a good escape until version
26.03.2024 3:37, Wall, Stephen wrote:
> There is a third option.
> Create both p5-DBD-mysql4 and p5-DBD-mysql5 using the respective versions,
> and turn p5-DBD-mysql into a meta-port that uses DEFAULT_VERSIONS to select
> one of the two numbered ports. There is precedent for this in the current
On Mon, Mar 25, 2024 at 4:11 PM Sergei Vyshenski
wrote:
> Hi Remko,
>
> It seems that the situation may be even more complicated than you describe.
>
> Upstream of DBD-mariadb lately made some unfriendly steps which in
> certain conditions may cause conflicts (up to crashes) with MariaDB server.
Dear port maintainers,
The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this po
