[MDEV-21944] Remove TokuDB from Debian packaging? Created: 2020-03-14  Updated: 2020-04-23  Resolved: 2020-04-23

Status: Closed
Project: MariaDB Server
Component/s: Packaging, Platform Debian
Affects Version/s: 10.5
Fix Version/s: 10.5.3

Type: Bug Priority: Major
Reporter: Otto Kekäläinen Assignee: Otto Kekäläinen
Resolution: Fixed Votes: 0
Labels: TokuDB

Issue Links:
Relates
relates to MDEV-19780 Remove the TokuDB storage engine Closed

 Description   

While reviewing autobake-deb.sh I came across this commit:
https://github.com/MariaDB/server/commit/85bef794f7d7b61e9fc11f3d94e003c99a599b86

Adding a delete line in autobake-deb.sh seems odd. What was the motivation here? The git commit message is really short, there is no in-line comments and this is very confusing since all the TokuDB packaging is still there.

Do you serg want me to properly clean away all TokuDB packaging from debian/* ?



 Comments   
Comment by Marko Mäkelä [ 2020-03-14 ]

I believe that yes, TokuDB should be removed from all packaging of MariaDB Server 10.5.

MDEV-19780 gives reasons for removing the TokuDB from the MariaDB Server.

I submitted a commit for removing TokuDB, but serg was conservative and preferred to preserve the source code in the branch, and only disable it at compilation time, so that it could be enabled if someone really needs it for some reason.

A similar decision was made with regard to the XtraDB storage engine in MariaDB Server 10.2. The XtraDB source code is present as ‘dead weight’ in the 10.2 branch, and it was finally removed in the 10.3 branch.

Comment by Otto Kekäläinen [ 2020-04-05 ]

Disabled in Debian packaging in https://github.com/MariaDB/server/commit/1589cf1cb3048984240f025ddc0c82fb311827fc

Comment by Otto Kekäläinen [ 2020-04-23 ]

TokuDB packaging removed in https://github.com/MariaDB/server/commit/9cc1c74ca3391779d5f00ece09981d2932cf173b

Generated at Thu Feb 08 09:11:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.