Details
-
Task
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Currently one needs the pre-configured source available to build a storage plugin that's not included in MariaDB. For distribution purposes of those external storage plugins that is not really beneficial, since it most always involves shipping a custom, matching MariaDB package as well.
This can be worked around by installing the necessary headers manually to include them in the MariaDB package (which is what is done in the Slackware package for MySQL and in my SlackBuild script for MariaDB), but that's a distribution specific solution and IMHO would be much better solved upstream.
The corresponding MySQL Bug is: http://bugs.mysql.com/bug.php?id=44722
The approach taken:
- Install some extra headers that are needed for out-of-tree build in
/usr/include/mysql/private. In .deb put these in a separate package.
- Out-of-tree builder is still responsible for setting same value of options
like DBUG, SAFEMALLOC, and SAFE_MUTEX.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Sergei Golubchik [ serg ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Description |
Currently one needs the pre-configured source available to build a storage plugin that's not included in MariaDB. For distribution purposes of those external storage plugins that is not really beneficial, since it most always involves shipping a custom, matching MariaDB package as well. This can be worked around by installing the necessary headers manually to include them in the MariaDB package (which is what is done in the Slackware package for MySQL and in my SlackBuild script for MariaDB), but that's a distribution specific solution and IMHO would be much better solved upstream. The corresponding MySQL Bug is: http://bugs.mysql.com/bug.php?id=44722 |
Currently one needs the pre-configured source available to build a storage plugin that's not included in MariaDB. For distribution purposes of those external storage plugins that is not really beneficial, since it most always involves shipping a custom, matching MariaDB package as well. This can be worked around by installing the necessary headers manually to include them in the MariaDB package (which is what is done in the Slackware package for MySQL and in my SlackBuild script for MariaDB), but that's a distribution specific solution and IMHO would be much better solved upstream. The corresponding MySQL Bug is: http://bugs.mysql.com/bug.php?id=44722 ----------------------------------------------------------------------- The approach taken: - Install some extra headers that are needed for out-of-tree build in /usr/include/mysql/private. In .deb/.rpm, put these in a separate package. - Out-of-tree builder is still responsible for setting same value of options like DBUG, safemalloc, and safe_mutex. |
| Description |
Currently one needs the pre-configured source available to build a storage plugin that's not included in MariaDB. For distribution purposes of those external storage plugins that is not really beneficial, since it most always involves shipping a custom, matching MariaDB package as well. This can be worked around by installing the necessary headers manually to include them in the MariaDB package (which is what is done in the Slackware package for MySQL and in my SlackBuild script for MariaDB), but that's a distribution specific solution and IMHO would be much better solved upstream. The corresponding MySQL Bug is: http://bugs.mysql.com/bug.php?id=44722 ----------------------------------------------------------------------- The approach taken: - Install some extra headers that are needed for out-of-tree build in /usr/include/mysql/private. In .deb/.rpm, put these in a separate package. - Out-of-tree builder is still responsible for setting same value of options like DBUG, safemalloc, and safe_mutex. |
Currently one needs the pre-configured source available to build a storage plugin that's not included in MariaDB. For distribution purposes of those external storage plugins that is not really beneficial, since it most always involves shipping a custom, matching MariaDB package as well. This can be worked around by installing the necessary headers manually to include them in the MariaDB package (which is what is done in the Slackware package for MySQL and in my SlackBuild script for MariaDB), but that's a distribution specific solution and IMHO would be much better solved upstream. The corresponding MySQL Bug is: http://bugs.mysql.com/bug.php?id=44722 ---- The approach taken: * Install some extra headers that are needed for out-of-tree build in {{/usr/include/mysql/private}}. In {{.deb}}/{{.rpm}}, put these in a separate package. * Out-of-tree builder is still responsible for setting same value of options like {{DBUG}}, {{SAFEMALLOC}}, and {{SAFE_MUTEX}}. |
| Description |
Currently one needs the pre-configured source available to build a storage plugin that's not included in MariaDB. For distribution purposes of those external storage plugins that is not really beneficial, since it most always involves shipping a custom, matching MariaDB package as well. This can be worked around by installing the necessary headers manually to include them in the MariaDB package (which is what is done in the Slackware package for MySQL and in my SlackBuild script for MariaDB), but that's a distribution specific solution and IMHO would be much better solved upstream. The corresponding MySQL Bug is: http://bugs.mysql.com/bug.php?id=44722 ---- The approach taken: * Install some extra headers that are needed for out-of-tree build in {{/usr/include/mysql/private}}. In {{.deb}}/{{.rpm}}, put these in a separate package. * Out-of-tree builder is still responsible for setting same value of options like {{DBUG}}, {{SAFEMALLOC}}, and {{SAFE_MUTEX}}. |
Currently one needs the pre-configured source available to build a storage plugin that's not included in MariaDB. For distribution purposes of those external storage plugins that is not really beneficial, since it most always involves shipping a custom, matching MariaDB package as well. This can be worked around by installing the necessary headers manually to include them in the MariaDB package (which is what is done in the Slackware package for MySQL and in my SlackBuild script for MariaDB), but that's a distribution specific solution and IMHO would be much better solved upstream. The corresponding MySQL Bug is: http://bugs.mysql.com/bug.php?id=44722 ---- The approach taken: * Install some extra headers that are needed for out-of-tree build in {{/usr/include/mysql/private}}. In {{.deb}} put these in a separate package. * Out-of-tree builder is still responsible for setting same value of options like {{DBUG}}, {{SAFEMALLOC}}, and {{SAFE_MUTEX}}. |
| Status | In Progress [ 3 ] | Open [ 1 ] |
pushed to lp:~maria-captains/ourdelta/ourdelta-montyprogram-fixes/
so all new deb builds will have it
| Fix Version/s | 5.5.25 [ 10901 ] | |
| Fix Version/s | 5.3.7 [ 10700 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Fix Version/s | 5.5.24 [ 10703 ] | |
| Fix Version/s | 5.5.25 [ 10901 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Workflow | defaullt [ 11227 ] | MariaDB v2 [ 45143 ] |
| Workflow | MariaDB v2 [ 45143 ] | MariaDB v3 [ 65798 ] |
| Workflow | MariaDB v3 [ 65798 ] | MariaDB v4 [ 131912 ] |
This seems to be related as well, although it proposes a different solution (I think).
https://bugs.launchpad.net/maria/+bug/470580