-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 30/10/14 16:48, Alan Pevec wrote:
It seems to me that this should be reverted based on the information you've provided. This shouldn't have been merged given it pulls in this new runtime dependency, which may also pull in new kernel dependencies. I don't see any other way around this other than to revert the change.
+1
Too bad we don't seem to be tracking such non-pypi runtime deps explicitly, how about adding runtime-requirements.txt (or better name) ?
I totally agree we need to track it in some centralized manner. BTW I've raised the point once (among other things) at [1] though haven't received much traction on this part of the email. Maybe I should go further and start a thread on this specific point?.. Comments. I also believe that for Neutron, we should track all python dependencies for all plugins included in the tree, and I've raised that point before [2]. Though again, the idea was not received with great passion. Probably I'm bad at communicating stuff. ;) [1]: http://lists.openstack.org/pipermail/openstack-dev/2014-October/047847.html [2]: http://lists.openstack.org/pipermail/openstack-dev/2014-August/043057.html /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUUmJmAAoJEC5aWaUY1u57uDcIAJ077+2UwBKY+0lINpkBiazk O4AwbysB4yuS4hA5heyIaLQqxNtK7AE4FcTkLMHiM8tl2yH5gErDU4GsmRsEl0Mt 8NrK72OiaykltYa27TREt+zniEKxH1rNsHcrXQJSNmdGglZqUdLQuShUVemu41EA QcLeS41S+vzk6IhnnFy0x4cLudYQo0XEwZjbYz4sT7Fi9e2BjcWGVJLMPWup6bHO UJT/hMryzHSyce0jRfLwqbkw2NXRo2ey/GXqGbUaMMnTVs2OFHJ7Vy4lxmhw/hOO 1yL6vXzI4dpTz+81iKaHLLZc1PGmt0hIjEvFO7EGn/+QBotIwUAoJHoY+5a3YrY= =elw5 -----END PGP SIGNATURE-----