| Message ID | cover.1681738065.git.efraim@flashner.co.il |
|---|---|
| Headers | show |
| Series | Remove mysql | expand |
Am Mon, Apr 17, 2023 at 04:29:13PM +0300 schrieb Efraim Flashner: > I saw that a fix was applied to mysql on core-updates to have it build > with openssl-1.1, and I figured that rather than have a version that was > several years out of date (and surely had many many security > vulnerabilities) it would be better to try to just remove it. > `mariadb:dev` provides the `mysql_config` binary that some packages > search for so I used it as a drop-in replacement. Nothing seemed broken > to me after building some packages, so to the best of my knowledge of > these disparate packages and languages all is fine. From what one reads, this seems to be the route to go; so unless a mysql champion chimes in, I am in favour of this change once QA gives a green button. Would you suggest to remove mysql altogether in a later commit? Andreas
On Wed, Apr 19, 2023 at 12:51:46PM +0200, Andreas Enge wrote: > Am Mon, Apr 17, 2023 at 04:29:13PM +0300 schrieb Efraim Flashner: > > I saw that a fix was applied to mysql on core-updates to have it build > > with openssl-1.1, and I figured that rather than have a version that was > > several years out of date (and surely had many many security > > vulnerabilities) it would be better to try to just remove it. > > `mariadb:dev` provides the `mysql_config` binary that some packages > > search for so I used it as a drop-in replacement. Nothing seemed broken > > to me after building some packages, so to the best of my knowledge of > > these disparate packages and languages all is fine. > > From what one reads, this seems to be the route to go; so unless a > mysql champion chimes in, I am in favour of this change once QA gives > a green button. Would you suggest to remove mysql altogether in a > later commit? That's certainly my hope. I feel like it's already been abandoned by us when we switched to mariadb, and the last commit touching it was more than 2 years ago.
On Mon, Apr 17, 2023 at 04:29:13PM +0300, Efraim Flashner wrote: > I saw that a fix was applied to mysql on core-updates to have it build > with openssl-1.1, and I figured that rather than have a version that was > several years out of date (and surely had many many security > vulnerabilities) it would be better to try to just remove it. > `mariadb:dev` provides the `mysql_config` binary that some packages > search for so I used it as a drop-in replacement. Nothing seemed broken > to me after building some packages, so to the best of my knowledge of > these disparate packages and languages all is fine. > > Efraim Flashner (8): > gnu: sysbench: Build with mariadb. > gnu: ghc-mysql: Build with mariadb. > gnu: neko: Build with mariadb. > gnu: inspircd: Build with mariadb. > gnu: ulogd: Build with mariadb. > gnu: opensmtpd-extras: Build with mariadb. > gnu: sbcl-clsql: Build with mariadb. > gnu: cl-clsql: Build with mariadb. > > gnu/packages/benchmark.scm | 9 +-------- > gnu/packages/haskell-xyz.scm | 4 ++-- > gnu/packages/haxe.scm | 3 ++- > gnu/packages/irc.scm | 4 ++-- > gnu/packages/linux.scm | 6 +++--- > gnu/packages/lisp-xyz.scm | 18 ++++++++++-------- > gnu/packages/mail.scm | 4 ++-- > 7 files changed, 22 insertions(+), 26 deletions(-) > > > base-commit: 2d06dfc050114dba44e791d8decc8eaa705fee01 This patch was pushed almost a month ago, closing the bug now