[openstack-dev] [requirements] [packaging] How can Upper Constraints be used by packagers

Matthew Thode prometheanfire at gentoo.org
Thu May 12 16:01:52 UTC 2016

On 05/12/2016 09:57 AM, Igor Yozhikov wrote:
> Hello.
> According to proposed changes in G-R
> (https://etherpad.openstack.org/p/newton-global-requirements)  related
> to ranges/bounds I want to clarify situation for Linux packagers.
> Very often packages for requirements mentioned in requirements.txt or
> global-requirements  file are built using code versions set in lower
> bounds. Usage of broader range for requirements will lead to complex
> calculations of minimum version of requirement which will satisfy all of
> projects which are using it. From perspective of packaging - must be
> only one installed version of requirement in a system.
> To avoid this complexity and provide co-installability, upper
> constraints could be used as the source of minimal version for
> requirements in system package.

Hi, Gentoo packager here :D

The basic gist of it is that g-r.txt is what's expected to work and
u-c.txt is what's tested to work.  There have been specs out there to
test a lower-contraints.txt file but I haven't seen it go anywhere quite

-- Matthew Thode (prometheanfire)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160512/136874cb/attachment.pgp>

More information about the OpenStack-dev mailing list