So, this is my perspective in packing liberty for Gentoo.
We can have multiple versions of a package available to install, because
of this we generally directly translate the valid dependency versions
from requirements.
this
oslo.concurrency>=2.3.0 # Apache-2.0
becomes this
>=dev-python/oslo-concurrency-2.3.0[${PYTHON_USEDEP}]
Now what happens when I package something from mitaka (2.7.0 in this
case would be mitaka). It's undefined behaviour as far as I know.
Basically, I can see no reason why the policy of caps changed from kilo
to liberty, it was actually nice to package for liberty, I can see this
going very bad very quick.
Where are my caps?
--
Matthew Thode (prometheanfire)
__________________________________________________________________________
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
