[MacPorts] #66981: mariadb-10.11 @10.11.1_0 binaries aren't in the normal path

MacPorts noreply at macports.org
Thu Feb 23 10:46:14 UTC 2023


#66981: mariadb-10.11 @10.11.1_0 binaries aren't in the normal path
----------------------------+-----------------------
  Reporter:  adamfranco     |      Owner:  michaelld
      Type:  enhancement    |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.8.1
Resolution:                 |   Keywords:
      Port:  mariadb-10.11  |
----------------------------+-----------------------

Comment (by ryandesign):

 It is intentional that mariadb-10.11 and all of the other MySQL-compatible
 software do not install their binaries into /opt/local/bin. If they did
 that, they would conflict with one another, which we don't want.
 Considerable effort was expended to ensure that these conflicts do not
 occur, by moving the files out of /opt/local/bin and other common
 directories.

 mariadb-10.11 and all of the other MySQL-compatible ports do support the
 `sudo port select` mechanism; that is the method by which you are intended
 to obtain symlinks in /opt/local/bin to the programs you want to use. You
 can use it to see a list of available installed MySQL-compatible ports;
 for example on my system just now:

 {{{
 % sudo port select mysql
 Available versions for mysql:
         mariadb-10.11
         none (active)
 }}}

 To select it:

 {{{
 % sudo port select mysql mariadb-10.11
 Selecting 'mariadb-10.11' for 'mysql' succeeded. 'mariadb-10.11' is now
 active.
 }}}

 And then:

 {{{
 % which mysql
 /opt/local/bin/mysql
 % mysql --version
 mysql  Ver 15.1 Distrib 10.11.1-MariaDB, for osx12.0 (x86_64) using
 readline 5.1
 }}}

 To deselect it later:

 {{{
 % sudo port select mysql none
 Selecting 'none' for 'mysql' succeeded. 'none' is now active.
 % which mysql
 mysql not found
 }}}

 You are correct that the mariadb-10.11 port does not print a note
 informing the user of this capability, and ideally it should be enhanced
 to do so. Unfortunately right now it is the responsibility of each port
 that uses the `sudo port select` mechanism to implement that note
 manually. It would be better if the select portgroup handled it
 automatically but at present it does not.

-- 
Ticket URL: <https://trac.macports.org/ticket/66981#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list