[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#763866: dh_apache2 should allow renaming of config files



Package: apache2-dev
Version: 2.4.10-2
Severity: wishlist

The packaging recommendations suggest to name config files for
conf-available the same as the binary package name containing the file.
There is a lintian warning to check this recommendation.
This is fine for the file contained in the binary package, but a bit
awkward in the source package if you want to support multiple web
servers in a webapp. If you want to use dh_apache2 (which is a great
tool) the you have to call your apache config file debian/packagename.conf also
in the source package. But this conflicts with config files for other
webservers, which would likely be called that way too.

There are workarounds for this problem already, but they all seem ugly
to me:
* Just call the files for other webservers differently and deal with
  this in your debian/rules. This is not really a problem as only Apache
  has a debhelper extension at the moment.
* Don't use dh_apache2 to copy the config file.
* Ignore the lintian warning and have a file like
  packagename-apache.conf in confs-available
* use subdirectories in debian like debian/apache/packagename.conf,
  debian/lighthttpd/packagename.conf.

IMO the best way to deal with this would be to allow renameing of config
files with dh_apache2.

Gaudenz

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apache2-dev depends on:
ii  debhelper        9.20140817
ii  libapr1-dev      1.5.1-3
ii  libaprutil1-dev  1.5.3-3
ii  openssl          1.0.1i-2
ii  perl             5.20.1-1

apache2-dev recommends no packages.

apache2-dev suggests no packages.

-- no debconf information


Reply to: