[
https://issues.apache.org/jira/browse/QPID-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909349#comment-13909349
]
Justin Ross commented on QPID-5550:
-----------------------------------
A few more thoughts:
The release script does this:
{noformat}
if [ "PERL" == "$PERL" ]; then
mkdir qpid-${VER}/perl-qpid-${VER}
cp qpid-${VER}/cpp/bindings/qpid/perl/perl.i \
qpid-${VER}/cpp/bindings/qpid/perl/LICENSE \
qpid-${VER}/cpp/bindings/qpid/perl/Makefile.PL \
qpid-${VER}/cpp/bindings/qpid/perl/t/*.t \
qpid-${VER}/perl-qpid-${VER}
...
{noformat}
That last bit flattens the structure of the perl tree. Is that for a reason?
It strikes me as fragile and unnecessary.
If we must have these extra tarballs (I'm waiting for the rationale), they
should be as close as possible to a simple subtree copy.
> 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]
