The underlying problem is as you say that distutils and setuptools and wheel are all different, and until there is a PEP addressing this *and* implemented in both wheel and setuptools, we won't get consistent behaviour. I'm pretty sure Daniel Hoth is interested in making this happen - there have been threads about it on distutils-sig inside the last year, but we (me/sachi/steven) hadn't gotten onto it as a thing to help with. I suggest chatting to Daniel as a first point of call to see where his effort is at and what help is needed.
Note that we *need* the wheel and setuptools behaviour to be consistent, or we will have differences between distro package building, devstack, and ansible uses.. amongst others. -Rob On 11 June 2016 at 13:50, Morgan Fainberg <morgan.fainb...@gmail.com> wrote: > There has been a bit of back[1] and forth[2][3][4][5] between at least one > packaging group and a few folks who are trying to define data files (config) > in the setup.cfg to aid/ease installation within virtual environments. > > From what I can tell, there has been an issue with setuptools that makes > this a particularly sticky situation and difficult to address in PBR via an > option like --sysconfdir due to a disagreement between setuptools and > disttools disagreeing upon the meaning of "data-files". [6] > > Before this turns into a nightmare of add-patches/revert/add/revert and > making things highly inconsistent within OpenStack, I'd like to get feedback > from the packaging teams on where this impacts them. I know that a number of > folks carry effectively this patch internally to make working with VENVs > easier. > > We should absolutely address this in setuptools/distutils/etc but a clear > direction forward so that the projects under OpenStack remain consistent for > users, developers, and packagers would be good at this point. > > I know that keystone has had a lot of work done to ensure we can work in > most "general" environments, but installing the data-files within a VENV is > much more simple than a bunch of special casing to "find" the config files. > > In short, I think OpenStack needs to define (even if it's a short period of > time) what we consider "data-files", we can always revisit this when/if we > have a clear path forward via PBR, setuptools, disttools, etc. > > [1] https://review.openstack.org/#/c/322086/ > [2] https://review.openstack.org/#/c/326152/ > [3] http://git.openstack.org/cgit/openstack/neutron/tree/setup.cfg#n24 > [4] http://git.openstack.org/cgit/openstack/gnocchi/tree/setup.cfg#n87 > [5] http://git.openstack.org/cgit/openstack/aodh/tree/setup.cfg#n30 > [6] https://review.openstack.org/#/c/274077/ > > Cheers, > --Morgan > > __________________________________________________________________________ > 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 > __________________________________________________________________________ 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
