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 they're not going to use the swift backend. When I proposed a change [1] to move this from requirements to test-requirements (would still be needed there because of tests using the swift backend), others raised concerns about the impact this could have on operators who use the swift backend today and would be upgrading to Liberty. I believe everyone agreed this should not be in requirements, but the fact is that it has been, so operators may have (incorrectly) been depending on that during upgrades. If we remove it in Liberty, and there are changes in Liberty that require a newer version of swiftclient, how would those operators know that they need to upgrade swiftclient?Even if swiftclient was removed from requirements.txt, I would still keep it as a hard Depends: in Debian, so it would not change anything for (Debian) users.
I think this is perfectly find and it's a good thing. Upstream packages don't need to follow everything that happens downstream. From a downstream perspective, it's a requirement that is not needed neither in the CI nor in most of the development environments. Cheers, Flavio
Thomas __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-- @flaper87 Flavio Percoco
pgppnN17ZocFu.pgp
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
