Le 15/01/2013 11:51, Vít Ondruch a écrit :
shouldn't be the JavaScript exception [1] revisited?
I don't think the problem was really about the need to unbundle a
javascript library, but "how" to package it.
I see 2 solutions to use a system JS library:
1/ using a symlink in the application tree.
This is probably the simpler
(even if it imply, for apache, a FollowSymLinks option)
2/ using an Alias
ex: Alias /appname/jslibname /usr/share/jslibname
But this will requires 2 apache configuration files
- one in the app to define the alias
- one in the library to allow access to the library dir
3/ other web server
Don't know.
I have recently submit syntaxhighlighter for review[1] and have try to
allow both (httpd configuration in a sub-package to avoid dependency on
http in the main one).
So, I think we mainly need a packaging Guidelines for JavaScript, and
then, we'll be able to drop the exception.
Regards,
Remi.
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=895592