[openstack-dev] common global requirements

Joshua Harlow harlowja at yahoo-inc.com
Thu Aug 9 01:34:43 UTC 2012


Yippie, this will help for others that are building there own packages.

Thx!

On 8/8/12 6:08 AM, "Monty Taylor" <mordred at inaugust.com> wrote:

>Hey all!
>
>One of the goals from the last ODS was to have a common set of package
>requirements across all of the projects. After talking through a bunch
>of different options, the one that sucked the least was to have a global
>list that can be copied/synced from. To that end, we've gone through the
>list of everything that all of the packages declare that they use, have
>correlated that with what devstack _actually_ installs (it's not what
>you think in all cases) and made the initial list from that. It has been
>pushed to the openstack/requirements project in Gerrit and the
>openstack-common core team has core-approval access.
>
>What does this mean effectively today? Nothing.
>
>However, there is now a global list, and a utility with that global list
>to update the list of things in your project to match the versions found
>in the global list without adding new dependencies (python-swiftclient
>probably doesn't need django after all) It works pretty much the same as
>the openstack-common update.py script - but since it's a list, you don't
>_really_ have to use that script for any reason if you don't want to.
>
>Adding new dependency libraries to the project should be done via first
>getting a patch landed to the openstack/requirements project adding the
>library- then landing the patch in the project. That will allow the
>folks who focus on packaging and whatnot to look for problematic
>libraries (like M2Cryto wound up being) or problematic versions (glance
>thinks it wants 0.2.3 of anyjson right now, but a newer version is in
>ubuntu)
>
>Eventually, depending on how we feel about how this all works, there has
>been discussion about adding a test to milestone-proposed branches to
>ensure that package versions in projects are in sync with the global
>list. That allows people to drift some during a dev cycle, or to take a
>little bit to update to a newer version if it's a bit ugly.
>
>Have fun!
>Monty
>
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




More information about the OpenStack-dev mailing list