On Wed, Sep 11, 2013 at 10:02:24AM -0400, Darryl L. Pierce wrote: > Gordon was installing the qpid-cpp 0.24 sources [1], which failed due to > the LICENSE file for the Perl bindings not being present. After filling > out a JIRA for this [2] and a comment from Gordon, it seemed to me that > the qpid-cpp sources probably shouldn't even include the Perl, or other > language, bindings. Instead it should probably only carry the C++ client > and server code, and leave the bindings to the monolithic tarball that's > produced instead. > > So my question is this, should we trim what's included in the qpid-cpp > sources to be only the C++ client and server code, leaving the language > bindings for the separate source tarballs? > > [ ] Yes, remove the language bindings from qpid-cpp-${VER} > [ ] No, leave the language bindings in qpid-cpp-${VER} > > > [1] http://www.apache.org/dyn/closer.cgi/qpid/0.24/qpid-cpp-0.24.tar.gz > [2] http://issues.apache.org/jira/browse/QPID-5128
To clarify, since it may not be clear, I'm not asking to remove the bindings from the qpid-${VER} file (the "monolithic tarball" mentioned above), but removing them from the qpid-cpp tarball. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpUJCGhxDVfq.pgp
Description: PGP signature