[Pkg-javascript-devel] Bug#474913: javascript-common overrides /javascript globally

[Hendrik Jaeger]

Control: found 474913 javascript-common/11+nmu1

On Tue, 20 Aug 2013 10:36:35 +0000 "Jean-Michel =?utf-8?q?Vourg=C3=A8re?=" <jmv_deb at nirgal.com> wrote:
> Now that version 11 has hit testing (It only took over 1000 days),
> and that javascript-common no longer rewrites the alias on every reconfigure
> if the sysop disabled it, I don't see the point to separate apache2 bug from
> lighttpd one.

I just upgraded a machine I had disabled this config on with
```
a2disconf javascript-common
```
to bullseye and it was enabled again.
So I don’t see that it does not reenable it.

> The question is whether it is ok to use /javascript url namespace or not.

IMHO not.
I have multiple vhosts, none of which need this Alias but all of them get this.
The package is installed automatically as part of a dependency chain over two other packages, not by admin demand.

IMHO no package should automatically enable any Alias globally.
Any competent admin is able to enable such confs manually, or at least quickly figure out how to do that and that it’s necessary.
Packages should not interfere with a manually enabled, and even more so disabled, config snippet.
The safe/secure choice is IMHO to make the admin enable such snippets.