Here's the back story:
Base RHEL 6 has Qpid 0.14, which is a very old release. Our team wants to make a more recent version, 0.26, available for projects such as Open Stack. They are adopting CentOS as a platform and would like to use 0.26, which includes AMQP 1.0 support.
We can't package 0.26 for EPEL6 due to 0.14 being in the base.
So it was suggested to me in IRC to come here and ask for guidance. We would like to make our newer packages available for CentOS 6. What's the right path to follow?
On 07/05/14 22:27, Darryl L. Pierce wrote:
Here's the back story:
Base RHEL 6 has Qpid 0.14, which is a very old release. Our team wants to make a more recent version, 0.26, available for projects such as Open Stack. They are adopting CentOS as a platform and would like to use 0.26, which includes AMQP 1.0 support.
We can't package 0.26 for EPEL6 due to 0.14 being in the base.
So it was suggested to me in IRC to come here and ask for guidance. We would like to make our newer packages available for CentOS 6. What's the right path to follow?
SCL (softwarecollections.org) and/or COPR comes to mind ?
On 7 May 2014 14:27, Darryl L. Pierce dpierce@redhat.com wrote:
Here's the back story:
Base RHEL 6 has Qpid 0.14, which is a very old release. Our team wants to make a more recent version, 0.26, available for projects such as Open Stack. They are adopting CentOS as a platform and would like to use 0.26, which includes AMQP 1.0 support.
We can't package 0.26 for EPEL6 due to 0.14 being in the base.
So it was suggested to me in IRC to come here and ask for guidance. We would like to make our newer packages available for CentOS 6. What's the right path to follow?
Can it be packaged up as qpid026 ? The main issue you are going to run into with any of the solutions is how to deal with potential conflicts of a person having software which requires qpid014 and qpid026 required.
On 05/07/2014 09:55 PM, Stephen John Smoogen wrote:
Can it be packaged up as qpid026 ? The main issue you are going to run into with any of the solutions is how to deal with potential conflicts of a person having software which requires qpid014 and qpid026 required.
we could put this sort of an update into CentOS Plus - then the question turns around a bit into a : Does this update satisfy the prev api/abi and libpaths ? ie. is this a drop in replacement to the older code ?
- KB
If the updated qpid package is primarily for use with OpenStack, perhaps the rdo repos will be a good place? Then there is less concern over breaking scenarios that may not have been tested.
http://openstack.redhat.com/Repositories
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel-bounces@centos.org] On Behalf Of Karanbir Singh Sent: Friday, May 09, 2014 2:08 AM To: centos-devel@centos.org Subject: Re: [CentOS-devel] Providing newer versions of packages from base CentOS/RHEL
On 05/07/2014 09:55 PM, Stephen John Smoogen wrote:
Can it be packaged up as qpid026 ? The main issue you are going to run into with any of the solutions is how to deal with potential conflicts of a person having software which requires qpid014 and qpid026 required.
we could put this sort of an update into CentOS Plus - then the question turns around a bit into a : Does this update satisfy the prev api/abi and libpaths ? ie. is this a drop in replacement to the older code ?
- KB
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 05/09/2014 02:45 PM, Kay Williams wrote:
If the updated qpid package is primarily for use with OpenStack, perhaps the rdo repos will be a good place? Then there is less concern over breaking scenarios that may not have been tested.
if that is the primary target then yeah - perhaps RDO is the place to target this ( I know a bunch of RDO folks are on this list as well, comments ? )
- KB
On Wed, May 07, 2014 at 02:55:23PM -0600, Stephen John Smoogen wrote:
Can it be packaged up as qpid026 ? The main issue you are going to run into with any of the solutions is how to deal with potential conflicts of a person having software which requires qpid014 and qpid026 required.
That's an option. I'm doing something similar with Qpid 0.24 that is required by other projects by creating compat-qpid-cpp.
-
Darryl L. Pierce -
Fabian Arrotin -
Karanbir Singh -
Kay Williams -
Stephen John Smoogen