Open Stack

Radomir, maybe you can help me better understand where this would go. I
have a few questions.

First, can you point me to a time when horizon used system packages
successfully for JavaScript libraries? When I looked through the Debian and
Ubuntu packages I couldn't find the libraries horizon is using. I'm curious
to see this in action.

Front-end systems almost never use system packagers like this. Can you
point me to applications like horizon that use system packages this way? If
Horizon is going to go it virtually alone in this space, what will that
mean for our level of work and ability to have updates?

Thanks,
Matt

On Mon, Jan 19, 2015 at 3:45 AM, Radomir Dopieralski <openstack at sheep.art.pl
> wrote:

> On 16/01/15 18:55, Matthew Farina wrote:
> > Doug, there still is one open question. Distributing JavaScript
> > libraries via system packages is unusual. Because of that, most of the
> > JavaScript libraries used by horizon don't have existing packages. Who
> > will create and maintain the packages for these JavaScript libraries for
> > production? For example, most of the libraries aren't available as
> > debian or ubuntu packages.
>
> You are mistaken here. It's actually the other way around. Fedora and
> Debian packagers used to do heroic work with previous releases to
> unbundle the static files from Horizon and link to the system-wide
> JavaScript libraries installed from packages, because their packaging
> policies require that. The introduction of XStatic was supposed to
> merely simplify and formalize that process, but now it turns out that it
> is redundant, and we can cut a corner and save the packagers having to
> create all those dummy XStatic shims.
>
> --
> Radomir Dopieralski
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150120/090e300b/attachment.html>