On Tue, Jul 09, 2013 at 09:30:08PM +0200, Jimmy Jones wrote: > > > > For QPID-4417 on on RHEL5 I believe the Swig package will have the > > > > proper fix backported and released in future. > > > > > > I'll be great to get SWIG fixed upstread in RHEL5, however its not > > > currently fixed, plus some people might not update their packages anyway, > > > so RHEL5 users will almost certainly get subtly broken bindings. Wouldn't > > > it be better to reintroduce the minimum version check - only means when > > > people are building Qpid from source on RHEL5 they'll also need to build > > > SWIG from source, which they could even keep in their home directory. > > > > It won't matter if someone running RHEL5 hasn't updated their Swig > > version: Swig is a build dependency, not a runtime dependency, so it > > only matters that the RHEL5 box on which the package is created has the > > updated Swig package with the backported fix. > > I get that, but currently nobody's RHEL5 has a patch and AFAIK there are no > official or unofficial Qpid RPMs so most RHEL5 users will compile from source > and get broken bindings. What are the downsides of re-introducing the minimum > version check (it'll only affect build, not runtime)?
If we re-introduce the check then it won't build on RHEL5 since the only available version of Swig for it is 1.3.29. -- 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/
pgpKXDnyPJYn6.pgp
Description: PGP signature
