MariaDB is a database server that offers drop-in replacement functionality
for MySQL. MariaDB is built by some of the original authors of MySQL, with
assistance from the broader community of Free and open source software
developers. In addition to the core functionality of MySQL, MariaDB offers
a rich set of feature enhancements including alternate storage engines,
server optimizations, and patches.
MariaDB is primarily driven by developers at Monty Program, a company
founded by Michael "Monty" Widenius, the original author of MySQL, but
this is not the whole story about MariaDB. On the "About MariaDB" page you
will find more information about all participants in the MariaDB community,
including storage engines XtraDB and PBXT.
WWW: https://mariadb.org/
===> The following configuration options are available for mariadb101-server-10.1.45:
CONNECT_EXTRA=off: Enable ODBC and XML in CONNECT engine
DOCS=on: Build and/or install documentation
FASTMTX=off: Replace mutexes with spinlocks
MAXKEY=on: Change max key length from 1000 to 4000
====> Optional page compression
LZ4=off: LZ4 compression support
LZO=off: LZO compression support
SNAPPY=off: Snappy compression library support
====> Optional MariaDB storage engines
INNOBASE=off: Build InnoDB engine next to XtraDB
MROONGA=off: Mroonga Full Text Search engine
OQGRAPH=off: Open Query Graph Computation engine
SPHINX=on: SphinxSE engine
SPIDER=on: Partitioning and XA-transactions engine
TOKUDB=off: Fractal tree index tree data structure engine
====> Optional Mroonga features
ZMQ=off: ZeroMQ support
MSGPACK=off: MsgPack support
====> GSSAPI Security API support: you have to select exactly one of them
GSSAPI_BASE=on: GSSAPI support via base system (needs Kerberos)
GSSAPI_HEIMDAL=off: GSSAPI support via security/heimdal
GSSAPI_MIT=off: GSSAPI support via security/krb5
GSSAPI_NONE=off: Disable GSSAPI support
===> Use 'make config' to modify these settings
Remove expired ports:
2020-07-01 databases/mariadb101-client: Port will be removed when 10.5 is added,
please switch to a newer version
2020-07-01 databases/mariadb101-server: Port will be removed when 10.5 is added,
please switch to a newer version
2020-07-01 databases/mariadb102-server: Port will be removed when 10.5 is added,
please switch to a newer version
2020-07-01 databases/mariadb102-client: Port will be removed when 10.5 is added,
please switch to a newer version
databases/mariadb101-server: fix build on powerpc64 elfv2
Like other SQL servers, this port fails to build due to Clang bug:
Wrong types for attribute: inalloca nest noalias nocapture nonnull readnone
readonly signext sret zeroext byval dereferenceable(1)
dereferenceable_or_null(1)
%call54 = call signext i32 @my_atomic_cas32(i32* %62, i32* %64, %union.U_32
signext %65)
in function lf_hash_insert
fatal error: error in backend: Broken function found, compilation aborted!
databases/mariadb101-server: fix build on powerpc*
Follow what mariadb102 and newer do and don't include glibc-related headers.
Fixes build on powerpc*.
PR: 241146
Approved by: brnrd (maintainer timeout), linimon (mentor)
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Change cmake default behaviour to outsource.
Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
databases/mariadb101-server: 12 not broken with security/openssl
- Backport to 5.5 and 10.0 too
- See also https://reviews.freebsd.org/D17834
PR: 232944
Reported by: iron udjin gmail com
databases/mariadb101-server: Security update to 10.1.37
- Not broken on i386 since 10.1.36
- Broken with OpenSSL 1.1.x, use MariaDB 10.2 or 10.3
MFH: 2018Q4
Security: ec5072b0-d43a-11e8-a6d2-b499baebfeaf
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
For ports in `databases' category: remove redundant PKGMESSAGE assignment,
which is set appropriately by the b.p.m when `pkg-message' appears on the
SUB_FILES list.
databases/mariadb101-server: Fix mysql_limits
- 11-STABLE and 12-CURRENT add limits support to rc.subr(8)
leading to variable conflicts with rc.d/mysql
PR: 227225
Submitted by: 0mp
Fix databases/mariadb* hostname verification when building against LibreSSL
LibreSSL imported X509_check_host from BoringSSL. Unlike OpenSSL,
it doesn't calculate the length of the hostname passed in case
chklen/namelen == 0. This means that the check in MariaDB always
fails if built against LibreSSL. This forces adminstrators to disable
hostname verification, which weakens security (hence the MFH request below).
Note that the fix has no negative implications if built against OpenSSL,
as its implementation calls strlen(hostname) in case namelen == 0.
See also https://github.com/MariaDB/server/pull/562
Approved by: ssl blanket
MFH: 2018Q1
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
MySQL ports: Extend CONFLICTS_INSTALL in conflicting ports.
databases/mysqlwsrep56-server has been present for some time and
databases/mysqlwsrep57-server has been added recently. Both ports
conflict with other MySQL server ports and this has been reflected
in databases/mysqlwsrep5[67]-server/Makefile but must also be
reflected in all conflicting ports' Makefiles as well.
The conflicting ports are:
databases/mariadb100-server
databases/mariadb101-server
databases/mariadb102-server
databases/mariadb55-server
databases/mysql55-server
databases/mysql56-server
(Only the first 15 lines of the commit message are shown above )
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
databases/mariadb101-server: Update to 10.1.21
- Update to 10.1.21
- Fix patches that no longer cleanly apply
- Rename patches to new naming scheme
MFH: 2017Q1
Security: 4d2f9d09-ddb7-11e6-a9a5-b499baebfeaf
Do not use post-stage. Use post-install instead.
The only reason to use post-stage is because the port needs to do
"things" at a later time, like some plist manipulation.
While there, fold post-install in do-install targets when they are
defined.
PR: 214780
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
databases/mariadb(100|101)-server: Document ncurses requirement
Previously (maria55) only the client required ncurses, but for recent
versions of mariadb, the server also requires it.
databases/mariadb101-server: Update to 10.1.19
- Update to 10.1.19
- Use target-OPT-on not .if exists
- Remove OQGraph patches now included upstream
MFH: 2016Q4
Security: 9bc14850-a070-11e6-a881-b499baebfeaf
Fix data encryption at rest when building with LibreSSL
Replace RAND_SSLeay->bytes with arc4random_buf when using LibreSSL, as
it supports RAND_SSLeay only for ABI compatibility [0].
Note that the code in question in mariadb mentions that RAND_bytes
isn't guaranteed to not block and therefore uses these functions directly.
As LibreSSL implements RAND_bytes in terms of arc4random_buf, which
shouldn't block, the patch could also use RAND_bytes instead of
using arc4random_buf directly, but the current version of the patch
has been tested in production and might be less confusing overall.
Bumped revision, as this fixes a runtime problem.
[0]
https://github.com/libressl/libressl/blob/master/src/crypto/rand/rand_lib.c#L36
PR: 213577
Approved by: ssl blanket
databases/mariadb101: Fix stage-QA for client
THere were 5 new programs built and installed by both the client and
the server. This is not a unique case. Previously they were allocated
to the client and removed by the post-install target of the server. In
this case, they've already been allocated to the server, so we need a
new post-install target for the client to remove them from the stage
directory so stage-QA checks pass.
While here, remove the now-unnecessary DragonFly configure argument
and change the backtick in a comment to an apostrophe to avoid the
makefile being interpreted as a shell script by some editors. Also
remove redundant forward slashes on the server post-install target.
Approved by: just-fix-it
databases/mariadb101: Fix OPSYS logic
The intent was to check for GSSAPI BASE option set on FreeBSD 9, but
the effect was an IGNORE set for all non-FreeBSD platforms. Fix the
logic to its original intent under the just-fix-it blanket.
databases/mariadb101-server: Update to 10.1.16
- Update to latest version 10.1.16
- Switch from USE_OPENSSL to USES= ssl
- Switch from USE_MYSQL to USES= mysql
- Switch from WANT_MYSQL_VER to USES= mysql:101m
- Fix liblz4 linking for mroonga
- Register MROONGA lz4 depends
- Register libxml2 depends
Fix usage of WITH_OPENSSL_BASE, WITH_OPENSSL_PORT and OPENSSL_PORT.
WITH_OPENSSL_* can't be set after bsd.port.pre.mk.
Fold all other usage into using SSL_DEFAULT == foo
PR: 210149
Submitted by: mat
Exp-run by: antoine
Sponsored by: The FreeBSD Foundation, Absolight
Differential Revision: https://reviews.freebsd.org/D6577
databases/mariadb101-{server,client}: Update to 10.1.14
- Update to version 10.1.14
- Remove fix for MDEV-9529
- Add new header files
- Add new MySQL to MariaDB migration script
databases/mariadb101-server: Fix i386, GSSAPI & Engine build issues
- Add USES=compiler:c++11-lib
- Use both deprecated -DPLUGIN_${engine} and new -DWITHOUT_${engine}
to disable engines (fixes engines not being disabled)
- Add IGNORE for GSSAPI_BASE on FreeBSD < 10, version is too old
- Add IGNORE for TokuDB, upstream not supported on 32-bit platforms
- Add IGNORE on i386, currently broken with clang [1]
[1] https://jira.mariadb.org/browse/MDEV-9627
Reviewer by: koobs (mentor)
Approved by: koobs (mentor)
Differential Revision: D5478
databases/mariadb101-{client,server}: Add missing patches
- Patches that were non-existent in the source of the repocopy
(mariadb100-*) were not part of the initial commit
Differential Revision: D3953
[NEW PORTS] databases/mariadb101-{server,client}: 10.1.11
MariaDB is one of the most popular database servers in the world. It's made
by the original developers of MySQL and guaranteed to stay open source.
Notable users include Wikipedia, Facebook and Google.
MariaDB turns data into structured information in a wide array of
applications, ranging from banking to websites. It is an enhanced, drop-in
replacement for MySQL. MariaDB is used because it is fast, scalable and
robust, with a rich ecosystem of storage engines, plugins and many other
tools make it very versatile for a wide variety of use cases.
MariaDB is developed as open source software and as a relational database
it provides an SQL interface for accessing data. This latest versions of
MariaDB also include GIS and JSON features.
WWW: http://mariadb.org/
Reviewed by: koobs (mentor), feld (mentor)
Approved by: koobs (mentor), feld (mentor)
Differential Revision: D3953
