Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-5550

Simplify binding artifacts and build metadata

    Details

      Description

      Right now we build special tarballs for the perl and wrapped python bindings of the messaging api in the release.sh script.

      First, what motivates this? Wouldn't be simpler from a packaging standpoint to simply build these when you build the C++ parts of the messaging api, using just the one cpp source tarball?

      Second, this logic belongs in the cpp subtree, not in the release.sh script. We can call into any "make special dist variant" targets we may need from the release script.

        Attachments

          Activity

            People

            • Assignee:
              mcpierce Darryl L. Pierce
              Reporter:
              justi9 Justin Ross
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: