On 08/16/2016 05:38 PM, Brant Knudson wrote: > s bindep.txt meant to be used by anything other than OpenStack CI? (As > in, are packagers going to rely on it?) > > In keystone's bindep.txt, we have packages listed like: > > |libldap2-dev [platform:dpkg] | > > > -> Which is only needed if you install with keystone[ldap] (see > keystone's setup.cfg[1]). > > | > | > > | > > |libsqlite3-dev [platform:dpkg] | > > > -> Which is only needed for unit tests. > > .. and maybe others that aren't needed in all deployments. > > So there's a use case for a) integrating with extras, and b) a > "test-bindep.txt". > > Maybe this is supported already or is known work to do, or maybe > somebody's looking for something to work on. > > [1] http://git.openstack.org/cgit/openstack/keystone/tree/setup.cfg#n28 > | > > -- > - Brant
I look at it (as a packager), though it is somewhat dubious as to whether or not what's there is actually needed. Having test-bindep.txt like we have test-requirements would be helpful. -- -- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__________________________________________________________________________ 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
