Summary: | audio/murmur - including mysql prevents using mariadb or another version of mysql | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx <mafsys1234> |
Component: | Individual Port(s) | Assignee: | Mark Felder <feld> |
Status: | Closed Works As Intended | ||
Severity: | Affects Only Me | CC: | brnrd, mafsys1234, vvd |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(feld) |
Version: | Latest | ||
Hardware: | arm | ||
OS: | Any |
Description
xxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxxXXxx
2019-12-18 23:33:42 UTC
Maybe time to replace the default mysql port from mysql57 to mariadb104? I'm using it as the default mysql port for more than 5 years. (In reply to VVD from comment #1) We could really benefit from a PROVIDES/REQUIRES relationship expression for dependencies so these things are simply interchanged... The only option for users in this situation is to build their own packages with the default MySQL server changed. This is a systemic problem that is beyond the scope of a single port/package. (In reply to Mark Felder from comment #2) Agree. If somebody need non-standard mysql port or any port with non-default options - he must build this port self. But we can create separate PR with replace default mysql port from 5.7 to 10.5m. |