thanks for the proposal, Doug. I need an example to understand how things will work out...
so, let me use a real-life example (version numbers are made up): openstackdocstheme uses sphinx and needs sphinx 1.6.0 or higher but knows version 1.6.7 is broken. So, openstackdocstheme would add to its requirements file: sphinx>=1.6.0,!=1.6.7 Any project might assume they work with an older version, and have in their requirements file: Sphinx>=1.4.0 openstackdocstheme The global requirements file would just contain: openstackdocstheme sphinx!=1.6.7 The upper-constraints file would contain: sphinx===1.7.1 If we need to block sphinx 1.7.x - as we do right now - , we only update requirements repo to have in global requirements file: openstackdocstheme sphinx!=1.6.7,<1.7.0 and have in upper-constraints: sphinx===1.6.6 But projects should *not* add the cap to their projects like: sphinx>=1.6.0,!=1.6.7,<=1.7.0 Is that all correct? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: 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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev