Reviewing all the constraints work, I see that repositories have created some workaround around requirements install for one of these two legimit reasons - most often using tools/tox_install.sh from tox.ini for it:
1) The repository is a dependency of another one and uses constraints, so edit upper-constraints file and allow git install. Example: http://git.openstack.org/cgit/openstack/ironic-lib/tree/tools/tox_install.sh 2) Install a package that is not on pypi. This is typical neutron or horizon. Example: http://git.openstack.org/cgit/openstack/neutron-lbaas/tree/tools/tox_install.sh Note there's a third usage as well: Install packages that are not in global-requirements but let's leave that use case out of this discussion. For 2, Robert Collins has started in https://review.openstack.org/#/c/252680 a way to check out the required repos - but that change is incomplete and looks orphaned. Instead of several projects copying and adopting these files - and thus having them in various state in repositories - what can we do to make it easier for developer and projects to address these two problems? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
