diff options
| author | Sebastian Kemper <sebastian_ml@gmx.net> | 2020-06-13 19:55:47 +0200 |
|---|---|---|
| committer | Sebastian Kemper <sebastian_ml@gmx.net> | 2020-06-13 20:05:08 +0200 |
| commit | c6f6d1d71dbbc9bd0bbb8ee1d58bb5dad978f3df (patch) | |
| tree | 062d9e8108e1e51b53e4693ac098065b0d0cb0dd /lang/python/python-more-itertools | |
| parent | 435e5077f817bd0d506282007c545c67a0586570 (diff) | |
mariadb: move some binaries
Even though I think that mysql_upgrade is a client package (it depends
on the mysql client and it's in the "client" directory in the source
tree, for instance), upstream laid it out differently. Since upstream
commit ec586f5 mysql_upgrade is to be considered a part of the server,
because the COMPONENT argument in the MYSQL_ADD_EXECUTABLE macro is set
to "Server".
That means that mysql_upgrade is only installed when the server is. So
we need to move it back to the server package, otherwise we will have a
build failure when mariadb-client is selected while mariadb-server is
not. This particular build failure was recently a topic on
openwrt-devel.
Some more binaries are moved, following the layout visible in
"man/CMakeLists.txt", to make sure we follow upstream's vision with
regards to how the binaries are packaged.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Diffstat (limited to 'lang/python/python-more-itertools')
0 files changed, 0 insertions, 0 deletions
