qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darryl L. Pierce" <dpie...@redhat.com>
Subject Re: 0.18 inclusion request - Perl upstream tarball changes
Date Fri, 13 Jul 2012 16:48:03 GMT
On Fri, Jul 13, 2012 at 04:45:46PM +0100, Robbie Gemmell wrote:
> As Gordon mentioned, I did indeed mean the other wrappers for the C++
> client rather than the python etc clients, and that adding to the output of
> release.sh is differnet than just adding support to a component build to
> produce a new artifact. It is however reasonable to note that we are
> actually releasing duplicate copies of the source for the python client.
> 
> I'm not actually suggesting it is wrong to add such an artifact for the
> Perl bits, just noting that it was disussed before that we consider moving
> away from publishing multiple artifacts for the same source and so should
> possibly be discussed before we go doing it again for some more bits but
> not others and becoming even more inconsistent than we already are now.

That's fine. I'm open to suggestions as to what others think is an
appropriate way to go. My goal is to have only what's absolutely
necessary in the upstream for the Perl bindings so that it can be a
top-level package of its own.

-- 
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/


Mime
View raw message