Skip site navigation (1)Skip section navigation (2)


| raw e-mail | index | archive | help
--000000000000ffab180614863e46
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Mar 25, 2024 at 4:11=E2=80=AFPM S=
ergei Vyshenski &lt;<a href=3D"mailto:svysh.fbsd@gmail.com" target=3D"_blan=
k">svysh.fbsd@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi=
=C2=A0
Remko,</div><div><br></div><div>It seems that the situation may be even mor=
e complicated than you describe.<br><br></div><div>Upstream of DBD-mariadb =
lately=C2=A0made some unfriendly steps which in certain=C2=A0conditions may=
 cause conflicts (up to crashes) with MariaDB server. It is the reason why =
DBD-mysql has been a good escape until=C2=A0version=C2=A0
DBD-mysql-5.004 appeared this March. Looks like a software war between 3 up=
steams, from which we had better keep aside (and even move as far as to Pos=
tgreSQL or such).</div><div><br></div><div>Some of my ports implicitly depe=
nd on a couple (MariaDB + DBD-mysql), and hence they are broken today.=C2=
=A0</div><div><br></div><div>Let me vote to preserve=C2=A0the old name p5-D=
BD-mysql for the last good and working version, and create a new port named=
 p5-DBD-mysql-5 or whatever.</div><div><br></div><div>Regards, Sergei</div>=
</div></blockquote><div><br></div><div>Hi,</div><div><br></div><div><div>In=
 addition to whatever y&#39;all decide about p5-DBD-mysql, I would ensure t=
hat=C2=A0p5-DBD-MariaDB can be installed and working along side it while st=
ill depending on=C2=A0mysql57-client.</div><div><br></div><div>A failed wor=
karound when I was hit with this some weeks ago was to use p5-DBD-MariaDB, =
but it was being marked as &quot;in conflict&quot; with whatever was gettin=
g pulled in for p5-DBD-mysql. I was not aware of issues with upstream DBD::=
MariaDB, but that might cause complications to what I&#39;m suggesting.</di=
v><div><br></div><div>My &quot;fix&quot; was to install mysqll57-client fro=
m Ports, then an older version of DBD::mysql from CPAN.</div><div><br></div=
><div>In any case, I appreciate that this is being addressed.</div><div><br=
></div><div>Cheers,</div><div>Brett</div></div><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Mar 25, 2024 at 1=
1:25=E2=80=AFPM SirDice &lt;<a href=3D"mailto:sirdice@gmail.com" target=3D"=
_blank">sirdice@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div dir=3D"ltr"><div>All,</div><div><br></div><di=
v>I took over maintainership of p5-DBD-mysql last week. Apparently I unwitt=
ingly managed to poke a hornets nest. Upstream author changed the code to m=
ake it only compatible with MySQL 8.x. I&#39;ve tried patching out some of =
those changes but it requires quite an effort and is, in the end, unmaintai=
nable. So currently it is broken if you change the default mysql to MariaDB=
. <br></div><div><br></div><div>At the moment I see a couple of options</di=
v><div><br></div><div>1) leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysql=
4 &#39;legacy&#39; version port. <br></div><div>2) &#39;downgrade&#39; p5-D=
BD-mysql to 4.051 and add a p5-DBD-mysql5 &#39;new&#39; version port.</div>=
<div><br></div><div>#1 works for the default MySQL (still at 8.0) but break=
s if trying to build with MariaDB. Arguments are made that those ports shou=
ld switch to p5-DBD-mariadb instead. But this causes another set of problem=
s, it&#39;s not a drop-in replacement and some ports seem to have problems =
with DBD-MariaDB. Those ports could switch to the &#39;legacy&#39; version =
until those issues are resolved upstream. #1 also poses a problem if the de=
fault is switched to MariaDB and ports haven&#39;t been updated yet to depe=
nd on p5-DBD-mariadb or p5-DBD-mysql4. <br></div><div><br></div><div>#2 is =
probably the &#39;quickest&#39; fix, it restores the status quo. Ports coul=
d include=20
p5-DBD-mysql5 if they have a requirement for the new version (and add a res=
triction to only build with MySQL 8.x). <br></div><div><br></div><div>While=
 typing this out, trying to get some advice, I&#39;m inclined to go for #2.=
 But how can I go back a version? Bump PORTEPOCH?</div><div><br></div><div>=
Sorry for the noise this caused. It wasn&#39;t intended.=C2=A0</div><div><b=
r></div><div>Greetings,</div><div><br></div><div>Remko C. aka SirDice<br></=
div><div><br></div></div>
</blockquote></div></div>
</blockquote></div></div>

--000000000000ffab180614863e46--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>