On Wed, Jan 20, 2016 at 12:34 PM Sander Hoentjen <san...@hoentjen.eu> wrote: [snip]
> > https://fedoraproject.org/wiki/Packaging:JavaScript > Yeah I read that, but is says "Please note that this section really only > applies to JavaScript libraries intended for use on the web." so I am > not sure that applies to my case. > It also doesn't thoroughly cover these use cases: 1. how to handle customized embedded forks of a JavaScript library in upstream, 2. how to deal with JavaScript resources which upstream Java packages embed in their WARs (should the maintainer have to rewrite significant portions of upstream code to make these resources available from another location in the filesystem?), 3. applications which require the same shared JavaScript resources but with slightly different flags set in the source (to control style, or behavior), 4. how to package a single upstream project which many projects use which contains a combination of images, styles, JavaScript, and other resources, in a well-known hierarchical structure (like Bootstrap)
-- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
