On 30 July 2015 at 09:38, Ian Cordasco wrote:
>
>
> On 7/29/15, 13:27, "William M Edmonds" wrote:
>
>>
>>> From: Doug Hellmann
>>> To: openstack-dev
>>> Date: 07/28/2015 07:59 PM
>>> Subject: Re: [openstack-dev] [
On 30 July 2015 at 02:48, Doug Hellmann wrote:
> Excerpts from Louis Taylor's message of 2015-07-29 15:25:33 +0100:
>> On Tue, Jul 28, 2015 at 07:55:54PM -0400, Doug Hellmann wrote:
>> > I replied on both patches, but I'll repeat it here for a broader
>> > audience:
>> >
>> > Please set up an "ext
On 7/29/15, 13:27, "William M Edmonds" wrote:
>
>> From: Doug Hellmann
>> To: openstack-dev
>> Date: 07/28/2015 07:59 PM
>> Subject: Re: [openstack-dev] [glance] Removing python-swiftclient
>
>> from requirements.txt
>>
>
>
>
So helpful! Thank you.
On Wed, Jul 29, 2015 at 7:48 AM, Doug Hellmann
wrote:
>
> There is some documentation in the pbr manual
> (http://docs.openstack.org/developer/pbr/#extra-requirements). The
> feature is implemented throughout the packaging tool chain now.
>
>
Ah, excellent! PEP 0426 see
> From: Doug Hellmann
> To: openstack-dev
> Date: 07/28/2015 07:59 PM
> Subject: Re: [openstack-dev] [glance] Removing python-swiftclient
> from requirements.txt
>
> I replied on both patches, but I'll repeat it here for a broader
> audience:
>
> Pleas
Excerpts from Louis Taylor's message of 2015-07-29 15:25:33 +0100:
> On Tue, Jul 28, 2015 at 07:55:54PM -0400, Doug Hellmann wrote:
> > I replied on both patches, but I'll repeat it here for a broader
> > audience:
> >
> > Please set up an "extras" entry for each backend instead of just
> > removi
Excerpts from Clay Gerrard's message of 2015-07-28 19:25:04 -0700:
> Doug,
>
> I believe our glance friends are not the only project with some open
> questions on dealing with the "required dependency for optional plugin"
> use-case. You've made a recommendation to leverage some python tooling
>
On Tue, Jul 28, 2015 at 07:55:54PM -0400, Doug Hellmann wrote:
> I replied on both patches, but I'll repeat it here for a broader
> audience:
>
> Please set up an "extras" entry for each backend instead of just
> removing the dependencies. That will signal to users that you know
> what dependenci
On 2015-07-28 19:25:04 -0700 (-0700), Clay Gerrard wrote:
[...]
> I'd be more curious for the documentation if you have any idea where I
> might look for it? Is this a feature of pkg_resources, distutils,
> setuptools, pbr? What exactly does describing dependencies via this
> "extras" key afford?
Doug,
I believe our glance friends are not the only project with some open
questions on dealing with the "required dependency for optional plugin"
use-case. You've made a recommendation to leverage some python tooling
functionality that I'm not familiar with. I was hoping I could probe you
to el
Excerpts from William M Edmonds's message of 2015-07-28 18:34:29 -0400:
>
> > From: Flavio Percoco
> > To: "OpenStack Development Mailing List (not for usage questions)"
> >
> > Date: 07/28/2015 07:36 AM
> > Subject: Re: [openstack-de
> From: Flavio Percoco
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 07/28/2015 07:36 AM
> Subject: Re: [openstack-dev] [glance] Removing python-swiftclient
> from requirements.txt
>
> On 28/07/15 09:15 +, Kuvaja, Erno wro
On 28/07/15 10:29 +0200, Thomas Goirand wrote:
On 07/27/2015 11:42 PM, William M Edmonds wrote:
python-swiftclient is only needed by operators that are using the swift
backend, so it really doesn't belong in requirements.txt. Listing it in
requirements forces all operators to install it, even if
On 28/07/15 09:15 +, Kuvaja, Erno wrote:
I do agree, we don’t depend or are cleaning the other clients out of the glance
dependencies as well and I think swift should not be there either.
The default store is filesystem store and if something is depending on the
actual store clients it sho
I do agree, we don't depend or are cleaning the other clients out of the glance
dependencies as well and I think swift should not be there either.
The default store is filesystem store and if something is depending on the
actual store clients it should be either glance_store or deployer (well fo
On 07/27/2015 11:42 PM, William M Edmonds wrote:
> python-swiftclient is only needed by operators that are using the swift
> backend, so it really doesn't belong in requirements.txt. Listing it in
> requirements forces all operators to install it, even if they're not
> going to use the swift backen
16 matches
Mail list logo
