> On Jan 16, 2015, at 12:55 PM, Matthew Farina <m...@mattfarina.com> 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. > > Updating a JavaScript dependency, such as angular, would mean each of the > system packages needs to be updated as well as the Horizon project. Would > would this process look like with packages on different systems needing > updates? > > Using bower for development and system packages for production doesn't appear > to be ready to start using.
We have, so far, relied on the distributors to build packages in whatever way works for their tools. What is it about JavaScript libraries that makes packaging them “unusual”? If we’re going to continue to rely on distributors to handle the packaging, the next step is to get some of the distribution packagers to chime in on what else might be useful to make their jobs easier. We’ve collaborated in the past by adding features or writing some of our own tools (that’s part of what led to pbr being created for python packages, for example). This thread is fairly long, so you might want to start a new one with an appropriate subject line to attract the right input. Was there a spec for this work? If not, that would be useful to have. > > On Fri, Jan 16, 2015 at 12:09 PM, Doug Hellmann <d...@doughellmann.com > <mailto:d...@doughellmann.com>> wrote: > > > On Jan 16, 2015, at 11:33 AM, Drew Fisher <drew.fis...@oracle.com > > <mailto:drew.fis...@oracle.com>> wrote: > > > > On 1/16/15 9:08 AM, Doug Hellmann wrote: > >> We are, and as this conversation has veered off in a destructive > >> direction, I think we should back up and look at the compromise Radomir > >> posted [1] to see if that solves the original technical problem we all > >> have. > >> > >> Does having the requirements specified in a JSON file, without requiring > >> a specific build tool to install the files, solve the packaging, > >> testing, and deployment issue on platforms where node.js isn’t supported > >> natively right now? > > > > For Solaris, yes. We can make that work. Thanks, Radomir for the > > suggestion. > > Great! > > Doug > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <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
__________________________________________________________________________ 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
