mariadb/debian/mariadb-client-core.install

usr/bin/mariadb
usr/bin/mariadb-check
usr/bin/my_print_defaults
usr/share/man/man1/mariadb-check.1
usr/share/man/man1/mariadb.1
usr/share/man/man1/my_print_defaults.1
MDEV-21303 Make executables MariaDB named To change all executables to have a mariadb name I had to: - Do name changes in every CMakeLists.txt that produces executables - CREATE_MARIADB_SYMLINK was removed and GET_SYMLINK added by Wlad to reuse the function in other places also - The scripts/CMakeLists.txt could make use of GET_SYMLINK instead of introducing redundant code, but I thought I'll leave that for next release - A lot of changes to debian/.install and debian/.links files due to swapping of real executable and symlink. I did not however change the name of the manpages, so the real name is still mysql there and mariadb are symlinks. - The Windows part needed a change now when we made the executables mariadb -named. MSI (and ZIP) do not support symlinks and to not break backward compatibility we had to include mysql named binaries also. Done by Wlad 2020-03-20 15:41:54 +01:00			`usr/bin/mariadb`
			`usr/bin/mariadb-check`
Deb: Move my_print_defaults to MariaDB client core package The my_print_default is required by mytop which is also in the MariaDB client package, which in turn requires the client core package. This way it is ensured my_print_default is always available when mytop is installed. The my_print_defaults is also requires by the server logrotate files and mysqld_safe script etc, but this change is fine, since the server core package always depends on the MariaDB client core package anyway and they are both installed on server installations. Closes: #1566, #1581 2021-04-04 18:05:29 +02:00			`usr/bin/my_print_defaults`
Deb: Run 'wrap-and-sort -a' so comparison across releases is easier 2019-07-25 01:49:12 +02:00			`usr/share/man/man1/mariadb-check.1`
			`usr/share/man/man1/mariadb.1`
Deb: Move my_print_defaults to MariaDB client core package The my_print_default is required by mytop which is also in the MariaDB client package, which in turn requires the client core package. This way it is ensured my_print_default is always available when mytop is installed. The my_print_defaults is also requires by the server logrotate files and mysqld_safe script etc, but this change is fine, since the server core package always depends on the MariaDB client core package anyway and they are both installed on server installations. Closes: #1566, #1581 2021-04-04 18:05:29 +02:00			`usr/share/man/man1/my_print_defaults.1`