[
https://issues.apache.org/jira/browse/QPID-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910328#comment-13910328
]
Darryl L. Pierce commented on QPID-5550:
----------------------------------------
The goal there was to move the files needed by upstream packaging sources into
a directory with a name that matches the release. Both Debian and Fedora
expect, after exploding the sources, to find the top-level directory be named
${PROJECT}-${VERSION}. The above could be simplified to just be:
cp -r qpid-${VER}/cpp/bindings/perl/* qpid-${VER}/perl-qpid-${VER}
rather than explicitly copying each individual file. That would meet the simple
subtree requirement.
Regarding a rationale for having them, it makes it simpler for packages to work
with only the bindings if there's a source bundle that contains just what's
needed to build it; i.e., the Swig descriptor, license and language-only
sources. Ted and I had talked about this a few years ago, that there's enough
of a separation between the language bindings and the core C++ codebase that we
could conceivably decouple releasing bindings from the core C++ code.
> Simplify binding artifacts and build metadata
> ---------------------------------------------
>
> Key: QPID-5550
> URL: https://issues.apache.org/jira/browse/QPID-5550
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client, Packaging, Perl Client, Python Client
> Reporter: Justin Ross
> Assignee: Darryl L. Pierce
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
