Bug 242713

Summary: audio/murmur - including mysql prevents using mariadb or another version of mysql
Product: Ports & Packages Reporter: JustIgnoreMe <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 JustIgnoreMe 2019-12-18 23:33:42 UTC
I use mariadb101 on the device, but if I try to install murmur, it attempts to remove mariadb101 because mysql57-client needs to be installed.

Can we not have a package with mysql? If people want to use mysql then perhaps a separate murmur-mysql?

This is for use on a raspberry pi 2B. I use packages on it, so creating a native port build is not an option. I attempted to cross-build under poudriere on an AMD64 but that takes too long (gcc9 is a dependency and has been compiling for days!)

As a vote pro-removal of mysql, debian does not include it. It uses sqlite3.

Log output of install:
=============================================================================
The following 10 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
        mariadb101-server-10.1.41_1
        protobuf-c-1.3.1
        mariadb101-client-10.1.41_1

New packages to be INSTALLED:
        cyrus-sasl: 2.1.27
        libevent: 2.1.11
        mysql57-client: 5.7.27
        qt5-sqldrivers-mysql: 5.13.0
        murmur: 1.3.0_1

Installed packages to be UPGRADED:
        protobuf: 3.5.2_1,1 -> 3.9.2,1

Installed packages to be REINSTALLED:
        pkg-1.12.0 (options changed)

Number of packages to be removed: 3
Number of packages to be installed: 5
Number of packages to be upgraded: 1
Number of packages to be reinstalled: 1

The operation will free 151 MiB.
=============================================================================
Comment 1 VVD 2020-06-25 11:12:23 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.
Comment 2 Mark Felder freebsd_committer 2020-08-21 15:06:38 UTC
(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.
Comment 3 VVD 2020-08-21 17:28:39 UTC
(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.