[
https://issues.apache.org/jira/browse/QPID-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912858#comment-13912858
]
Darryl L. Pierce commented on QPID-5550:
----------------------------------------
>From a packaging perspective, trying to build them all in one package would be
>a headache since, if a bug is reported in any one part, we would have to
>rebuild the world to put out even a small fix.
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
