So just to be clear, as developers we:

1. have a bower.json listing the bower component to use,
2. use bower to fetch and install those to the bower_components directory
at the top level of the Horizon repos checkout, and
3. manually edit when we add a new bower component to
bower.json so it knows the appropriate static files to load from that

Is that correct?

The above will increase the burden on those adding or upgrading bower
components (they'll need to check the bower.json in the component for the
appropriate static files to link in) but will make life easier for the
re-packagers since they'll know which files they need to cater for in


On Mon Dec 22 2014 at 8:24:03 PM Radomir Dopieralski <>

> On 20/12/14 21:25, Richard Jones wrote:
> > This is a good proposal, though I'm unclear on how the
> > file is populated by a developer (as opposed to a
> > packager, which you described).
> It's not, the developer version is included in the repository, and
> simply points to where Bower is configured to put the files.
> --
> Radomir Dopieralski
> _______________________________________________
> OpenStack-dev mailing list
OpenStack-dev mailing list

Reply via email to