But these newer versions are not really CentOS-only? They could be used with RHEL if someone wanted/needed them?
Perhaps point users to the newer versions in the OpenStack (RDO) repos? Or create a separate qpid repo where newer versions can always be had (for use with either CentOS or RHEL)?
Seems cleaner (IMHO) than muddling the packages with a general repo like centos-plus.
Maybe the question is whether CentOS is providing a general solution for hosting repositories for newer-than-rhel packages?
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel- bounces@centos.org] On Behalf Of Darryl L. Pierce Sent: Tuesday, May 13, 2014 1:28 PM To: The CentOS developers mailing list. Subject: Re: [CentOS-devel] Creating a CentOS-only package
On Tue, May 13, 2014 at 09:01:53PM +0100, Karanbir Singh wrote:
the easy way of doing this would be to drop it into the Plus repo, that allows anything ( including stuff that over writes and replaces components from inside the base os repos ). however, that means that any other code that requires or benefits from the newer qpid would need to rely on the Plus repo ( and thereby potentially expose all packages, not just qpid, to the install ). Unless some sort of includepkg / excludepkg is done ( is messy, but many people can live
with it ).
With that in mind, what sort of use cases are you trying to target -
i
dont think we really quantified that in the prev thread.
The general use cases are projects, such as Open Stack, that are targeting CentOS and who would want to use an AMQP 1.0 messaging interface, like Open Stack.
We're also of course looking for more avenues for adoption of the Qpid and Proton projects and AMQP as a standard.
-- 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/