On Jul 2, 2012, at 6:40 PM, Monty Taylor <mord...@inaugust.com> wrote:
> Hey all! > > One of the tasks from the last ODS was to implement a single global > dependency list. Turns out the more you think about it, the more > important it is... because of the way we use devstack as part of the > gate, we actually _currently_ have a de facto global dependency list, > it's just not declared anywhere. (oops) > > Anyway - the original thought was to put the depends in > openstack-common. We'd use update.py to copy the depends in to the > project, so that projects could align on their own timeframe. > Additionally, we'd make the copy only copy in the versions from > openstack-common for package that were already listed in the target > project, so that we wouldn't add django to python-swiftclient, for instance. > > The mechanics of that all work and are ready - but then bcwaldon pointed > out that it didn't make a ton of sense for them to go in > openstack-common, since that has its own lifecycle and is a place for > common code to go - not just a catch all place. > > To that end, I took the code we had written for the update logic and put > it, along with the depends lists, into its own repo. I think we're ready > to start actually moving forward with it - but we've run up against the > hardest problem we every have: > > naming > > openstack-depends already got vetoed on IRC because it makes people > think of adult diapers. I'm proposing openstack-requires, since the > files we're talking about are actually python requirements files. > > Any objections? +0 on the name As an alternative, how about combining the requirements file with the other packaging related stuff from openstack-common and calling the result openstack-packaging? Doug _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp