Hi Marc, On 14.05.2012 23:37, Marc Haber wrote: > torrus-apache2 is a deprecated method of using torrus that should not > be used for new installs. We have documented this.
Fair enough, feel free to wontfix it, then. At some point you may consider moving the file to /usr/share/doc. >> * Do NOT declare a strong relation against apache2.2-common (or >> apache2-common as its natural successor). Instead recommend "apache2 | >> httpd" in your package relationships. > > We only support apache2, and we depend on apache2-mpm-prefork | > apache2, and conflict against apache2-mpm-worker and apache2-mpm-event We have documented how you can declare MPM dependencies in our packaging guide [1]. As MPM packages are gone given they are simple modules in 2.4, you can not conflict with a particular MPM anymore. Note, in a web application package you are only allowed to *warn* about conflicting MPMs, but not to *actually* change it in your maintainer scripts. This is, because web applications changing MPMs could result in a very complex and undefined outcomes. However, you can declare a MPM dependency and our tools will warn the user about your requirements. > > Do we need to change things for a package that is not recommended to > be used in wheezy and that will go away for wheezy+1? Chances are you won't. As the acknowledge by the release team is pending and we're short to freeze, it's not incredibly unlikely Apache 2.4 won't make it into Wheezy at all. [1] http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
