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

No Source RPMs ... (and so no "yum-builddep MariaDB-server" either)

Details

    Description

      The Knowledge Base article on "why we don't have SRPMs" says:

      "We are currently investigating using a source RPM generator as documented via a macro."

      < https://mariadb.com/kb/en/mariadb/documentation/getting-started/binary-packages/rpm/why-do-mariadb-rpms-not-include-the-source-rpm-srpms/ >

      I couldn't find any related Jira issue though, thus I've now submitted this one.

      Reason for this is that I'm missing the ability to say

        yum-builddep MariaDB-server

      to pull in all build dependencies required to compile MySQL from source.
      I don't even plan to build from SRPMs, but being able to install all required packages in a single step is pretty convenient even when building from source tarballs or directly from bzr / git ...

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14954 Build environment information seriously lacking

          • Major - Major loss of function.
          • Closed
          links to

          Web Link CPackRPM packaging of source package

          Activity

            Ascending order - Click to sort in descending order
            View 9 older comments
            serg Sergei Golubchik added a comment -

            1 and 2 are done.

            dbart, 3. is on you

            serg Sergei Golubchik added a comment - 1 and 2 are done. dbart , 3. is on you
            danblack Daniel Black added a comment -

            Nice work serg. Thankyou.

            danblack Daniel Black added a comment - Nice work serg . Thankyou.
            dbart Daniel Bartholomew added a comment -

            3 is done.

            4 is something I'll work with greenman on to make sure it updated documentation is ready for our first release with src.rpm files.

            serg: Which release do you expect will be the first one with this?

            dbart Daniel Bartholomew added a comment - 3 is done. 4 is something I'll work with greenman on to make sure it updated documentation is ready for our first release with src.rpm files. serg : Which release do you expect will be the first one with this?
            dbart Daniel Bartholomew added a comment - - edited

            For the docs, a new Building MariaDB from a src.rpm page will need to be created and this page will need to be updated:

            There might be other existing pages that also need to be updated, but this one needs to be updated for sure so that it mentions that some Distributions now have source RPMs available (after they're actually available of course).

            dbart Daniel Bartholomew added a comment - - edited For the docs, a new Building MariaDB from a src.rpm page will need to be created and this page will need to be updated: https://mariadb.com/kb/en/library/why-mariadb-rpms-dont-include-the-source-rpm-srpms/ There might be other existing pages that also need to be updated, but this one needs to be updated for sure so that it mentions that some Distributions now have source RPMs available (after they're actually available of course).
            serg Sergei Golubchik added a comment -

            I'll try to merge it into the upcoming 10.3 release, but if it'll take too long to merge, then the next 10.1.

            serg Sergei Golubchik added a comment - I'll try to merge it into the upcoming 10.3 release, but if it'll take too long to merge, then the next 10.1.

            People

              serg Sergei Golubchik
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.