| raw e-mail | index | archive | help
<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>= <br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon= , Mar 25, 2024 at 11:25=E2=80=AFPM SirDice <<a href=3D"mailto:sirdice@gm= ail.com">sirdice@gmail.com</a>> wrote:<br></div><blockquote class=3D"gma= il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2= 04,204);padding-left:1ex"><div dir=3D"ltr"><div>All,</div><div><br></div><d= iv>I took over maintainership of p5-DBD-mysql last week. Apparently I unwit= tingly 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= inable. So currently it is broken if you change the default mysql to MariaD= B. <br></div><div><br></div><div>At the moment I see a couple of options</d= iv><div><br></div><div>1) leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysq= l4 'legacy' version port. <br></div><div>2) 'downgrade' p5-= DBD-mysql to 4.051 and add a p5-DBD-mysql5 'new' version port.</div= ><div><br></div><div>#1 works for the default MySQL (still at 8.0) but brea= ks if trying to build with MariaDB. Arguments are made that those ports sho= uld switch to p5-DBD-mariadb instead. But this causes another set of proble= ms, it's not a drop-in replacement and some ports seem to have problems= with DBD-MariaDB. Those ports could switch to the 'legacy' version= until those issues are resolved upstream. #1 also poses a problem if the d= efault is switched to MariaDB and ports haven't been updated yet to dep= end on p5-DBD-mariadb or p5-DBD-mysql4. <br></div><div><br></div><div>#2 is= probably the 'quickest' fix, it restores the status quo. Ports cou= ld 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'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'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> --000000000000e6361b0614829c6a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>