Hi all. I see on freshports that MySQL in ports is at 8.0.23. Yet 8.0.25 has been out for a week, and 8.0.24 was released almost a month ago. `pkg audit` reports that 8.0.23 suffers from many CVEs.
Is it typical that this port does not stay more up-to-date?
I'm on 5.7 and this situation is unusual in the years up until this year (or maybe tail-end of last year).
One of the recent MySQL 5.7 updates seemed to be taking a long time to be released on FreeBSD so I thought "how hard can it be?" and downloaded the old and new versions and diffed them.
I thought there might be a hundred changes ... I was wrong!
I don't know why but Oracle/MySQL seem to stuff hundreds of other changes in each dot release (might have expected that with 8.0 but not the older 5.7). Entire build system changed or massively tweaked, SSL requirements changed, unrelated changes, etc. So what should be a reasonably-sized job becomes a monster. Thousands of changes ... are they all needed? What do they do? How do you test?
It made me appreciate the FreeBSD porters a lot more.
Doesn't help any of us waiting for the new versions to be released.
patch
work/mysql-5.7.34/sql/locks/shared_spin_lock.cc
at line 246 make both branches like #ifdef APPLE
my_atomic_store64(&this->m_exclusive_owner, reinterpret_cast<int64>(self));
change port Makefile
at CMAKE_ARGS => WITH_DEBUG=1 (from WITH_DEBUG=0)
kill all the patches in files/*
and it builds (with lots of warnings)
posted. lots of stuff breaks in inno-storage because -DUNIV_DEBUG is missing (so WITH_DEBUG=1)
also i dont know what side effects might be because i killed all the original patches (mostly of cmakefiles)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.