On 18 November 2014 10:59, Richard Jones <r1chardj0n3s at gmail.com> wrote: > On 17 November 2014 21:54, Radomir Dopieralski <openstack at sheep.art.pl> > wrote: > > - Bower in the development environment, > > - Bower configuration file in two copies, one for global-requirements, > > and one for the Horizon's local requirements. Plus a gate job that makes > > sure no new library or version gets included in the Horizon's before > > getting into the global-requirements, > > Could you perhaps elaborate on this? How do you see the workflow working > here? > > Given that Horizon already integrates with xstatic, it would be messy (and > potentially confusing) to include something so it *also* integrated with > bower. I was envisaging us creating a tool which generates xstatic packages > from bower packages. I'm not the first to think along these lines > http://lists.openstack.org/pipermail/openstack-dev/2014-March/031042.html > > I will be looking into creating such a tool today. > I wrote the tool today, and you can find it here: https://github.com/r1chardj0n3s/flaming-shame (github auto-named the repository for me - it's like it KNOWS) I've proposed to Thomas Waldmann that this be included in the xstatic package. It doesn't handle dependencies at all - I'm not sure it should or could sensibly. Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141118/558c32f6/attachment.html>