Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21108

Purposing patch for groonga engine's CMakeList

Details

    Description

      This purposed patch contains ( if not defined ) conditions inside of the groonga's and groonga-normalizer-mysql CMakeLists for the install path.

      Reason for this patch is that if groonga package is packaged separately, while installing it the conflict occurs between the installed files from mariadb-server.

      With this patch you have to only include two options to cmake and conflict is gone.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          anel Anel Husakovic added a comment -

          Hi ljavorsk,
          thank you for your patch.
          It would be great if you could create an pull request on github to be visible and evaluated by more developers.
          Please mention in description the version for which problem is occurring as well as cmake options you used with your patch so we could have better overview.
          Thanks.

          anel Anel Husakovic added a comment - Hi ljavorsk , thank you for your patch. It would be great if you could create an pull request on github to be visible and evaluated by more developers. Please mention in description the version for which problem is occurring as well as cmake options you used with your patch so we could have better overview. Thanks.
          robertbindar Robert Bindar added a comment -

          Merged PR contribution from ljavorsk

          robertbindar Robert Bindar added a comment - Merged PR contribution from ljavorsk

          People

            robertbindar Robert Bindar
            ljavorsk Lukas Javorsky
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.