On 07/15/2014 10:58:50 +0200, Flavio Percoco wrote: >On 07/15/2014 07:16 PM, Doug Hellmann wrote: >> On Tue, Jul 15, 2014 at 1:03 PM, Ken Giusti <kgiu...@gmail.com> wrote: >>> >>> These packages may be obtained via EPEL for Centos/RHEL systems >>> (qpid-proton-c-devel), and via the Qpid project's PPA [3] >>> (libqpid-proton2-dev) for Debian/Ubuntu. They are also available for >>> Fedora via the default yum repos. Otherwise, the source can be pulled >>> directly from the Qpid project and built/installed manually [4]. >> >> Do you know the timeline for having those added to the Ubuntu cloud >> archives? I think we try not to add PPAs in devstack, but I'm not sure >> if that's a hard policy. > >IIUC, the package has been accepted in Debian - Ken, correct me if I'm >wrong. Here's the link to the Debian's mentor page: > >http://mentors.debian.net/package/qpid-proton >
No, it hasn't been accepted yet - it is still pending approval by the sponsor. That's one of the reasons the Qpid project has set up its own PPA. >> >>> >>> I'd like to get the blueprint accepted, but I'll have to address these >>> new dependencies first. What is the best way to get these new >>> packages into CI, devstack, etc? And will developers be willing to >>> install the proton development libraries, or can this be done >>> automagically? >> >> To set up integration tests we'll need an option in devstack to set >> the messaging driver to this new one. That flag should also trigger >> setting up the dependencies needed. Before you spend time implementing >> that, though, we should clarify the policy on PPAs. > >Agreed. FWIW, the work on devstack is on the works but it's being held >off while we clarify the policy on PPAs. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev