mythweb interferes with apache config

[Joerg Delker]

Release: Ubuntu 18.04.2 LTS
mythweb: 2:29.1+fixes.20180414.329c235-0ubuntu3

When installing or updating mythweb, the post-install performs certain apache modifications, that are potentially harmful and not according to debian/ubuntu guidelines.

Issue:
On any post-install action originating from a install, update or dpkg-reconfigure, the packages creates a file /etc/apache2/sites-available/mythweb.conf and enables this configuration with "a2ensite" (which effectively symlinks it to /etc/apache2/sites-enabled).
While this may be confortable for unexperienced users, that do not care about their apache config, this is actually causing a lot of trouble in more sophisticated apache environments.

1. The config generated ("mythweb.conf") is no site-config (containing no virtual-hosts). Thus it belongs to /etc/apache2/conf-available rather than /etc/apache2/sites-available).
2. The config is forcefully enabled on every post-install run (incl. updates!), regardless of whether the system admin decided (for whathever reason) to disable the mythweb configuration or handling this in a different way. In fact, mythweb is enabled for every (!) site (virtual-host) served by apache this way.

I would suggest the following changes:
- Please honor Debian's way of configuring apache and create the mythweb configuration in /etc/apache2/conf-available.
- Do not re-enable this config on any update or reconfigure, if it was disabled before. Prefered alternative: Provide a debconf option, that disabled any apache configuration entirely.