Thanks, Radomir. How much detail from this discussion should be captured in the blueprint? I'm afraid I'm more familiar with the Python PEP process.
On Thu Jan 08 2015 at 11:38:57 PM Radomir Dopieralski < openst...@sheep.art.pl> wrote: > On 06/01/15 01:53, Richard Jones wrote: > > I think the only outstanding question is how developers and > > non-packagers populate the bower_components directory - that is, how is > > bower expected to be available for them? > > > > I think following the Storyboard approach is a good idea: isolate a > > known-working node/bower environment local to horizon which is managed > > by tox - so to invoke bower you run "tox -e bower <command>". No worries > > about system installation or compatibility, and works in the gate. > > > > Horizon installation (whenever a pip install would be invoked) would > > then also have a "tox -e bower install" invocation. > > > > Storyboard[1] uses a thing called nodeenv[2] which is installed through > > pip / requirements.txt to control the node environment. It then has > > bower commands in tox.ini[3] (though I'd just have a single "bower" > > environment to implement the tox command I suggest above. > > > > > > Richard > > > > [1] https://wiki.openstack.org/wiki/StoryBoard > > [2] https://pypi.python.org/pypi/nodeenv > > [3] https://git.openstack.org/cgit/openstack-infra/ > storyboard-webclient/tree/tox.ini > > > > I created a blueprint for this. > https://blueprints.launchpad.net/horizon/+spec/static-file-bower > -- > Radomir Dopieralski > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
