I totally agree with Michal Čihař, and this bug report should have been issued by (at least) changing /javascript to something less risky before releasing. I think even /javascript-common is much too common (sic) to think it'll not break a few websites. A company could use /javascript for its websites and have a /javascript-common for common javascript on all of its websites and thus be inconvenienced.
For the record : I've just tried to install rsslounge on an apache server, and the website was not working *at all*. The diagnosis was a bit tricky, there was no error in the server logfiles because of the local rewrites by rsslounge... In fact it was trying to access rsslounge's javascript in /usr/share/javascript-common/, where obviously the files were not available. I can see the point of this package, but I find it too intrusive. In fact, I find global Aliases too intrusive and I think they should never be defined for a whole server, but always on a per-vhost basis. We rarely need all aliases to be on all of our vhosts and sometimes it's a (small, I concede) security inconvenience. Here's what I suggest : - use /javascript-common-libs instead of /javascript and propagate the name change to the dependent packages. The name javascript-common-libs contains the package name and is not too common - javascript-common package should behave like phpmyadmin and ask the user - at install time - which web servers he'd like to automatically configure to use it Regards -- Loïc Gomez PS: maybe the bugs #474913 and #553173 could be merged.
