I have submitted a couple of changes to start us down the path to better
optional dependency support, as discussed below. There are still some
issues to be worked out, like how to specify a default for a particular
project (I punted on this for the oslo.messaging POC and left kombu as a
hard r
On 2014-02-12 18:22, David Koo wrote:
We could use a separate requirements file for each driver, following a
naming
convention to let installation tools pick up the right file. For
example,
oslo.messaging might include amqp-requirements.txt,
qpid-requirements.txt,
zmq-requirements.txt, etc.
y 12, 2014 at 1:42 PM To: Ben Nemec
mailto:openst...@nemebean.com>>, "OpenStack
Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [All]Optional dependencies and
requirements.txt
On Wed, Feb 12, 2014 at 3
"openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [All]Optional dependencies and
requirements.txt
>
>> Most of the reason for the #2 there is for plugins that taskflow can
>> use (but which are not required for all users). Ideally there would be
>>
g>>
> Date: Wednesday, February 12, 2014 at 1:42 PM To: Ben Nemec
> mailto:openst...@nemebean.com>>, "OpenStack
> Development Mailing List (not for usage questions)"
> mailto:openstack-dev@lists.openstack.org>>
> Subject: Re: [openstack-dev] [All]Optional depende
ck-dev@lists.openstack.org>>
Date: Wednesday, February 12, 2014 at 1:42 PM
To: Ben Nemec mailto:openst...@nemebean.com>>,
"OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [All]Optiona
On Wed, Feb 12, 2014 at 4:22 PM, David Koo wrote:
>
> If we're going to have more than one requirement file then may I propose
> something like a requirements.d directory and putting the files in that
> directory (and no need for a -requirements suffix)?
>
> requirements.d/
> global
>
> We could use a separate requirements file for each driver, following a naming
> convention to let installation tools pick up the right file. For example,
> oslo.messaging might include amqp-requirements.txt, qpid-requirements.txt,
> zmq-requirements.txt, etc.
If we're going to have more than o
On Wed, Feb 12, 2014 at 3:58 PM, Ben Nemec wrote:
> Hi all,
>
> This is an issue that has come up recently in tripleo as we try to support
> more varied configurations. Currently qpid-python is not listed in
> requirements.txt for many of the OpenStack projects, even though they
> support using
Hi all,
This is an issue that has come up recently in tripleo as we try to
support more varied configurations. Currently qpid-python is not listed
in requirements.txt for many of the OpenStack projects, even though they
support using Qpid as a messaging broker. This means that when we
insta
10 matches
Mail list logo
