Re: p5-DBD-mysql: Stuck between a rock and a hard place

26.03.2024 19:37, SirDice wrote: > On Tue, Mar 26, 2024 at 1:34 AM Eugene Grosbein > wrote: > > 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 >> i

Re: p5-DBD-mysql: Stuck between a rock and a hard place

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.

Re: p5-DBD-mysql: Stuck between a rock and a hard place

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

Re: p5-DBD-mysql: Stuck between a rock and a hard place

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

RE: p5-DBD-mysql: Stuck between a rock and a hard place

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