| | what's the point of having an apache2 package then? the package | | doesn't really depend on anything then, just that you have any | | implementation of apache2? | | Yes, what else would it depend on?
a specific version of apache2, much as the previous versions of the apache2 package had done. with apache2, version 2.2.3-2, there's no need to ever change the package again (for the most part). | | also, if another package depends on apache2 (>=2.2) then the apache2 | | package should depend on an implementation representative of the | | apache2 package's version. | | Why would any package depend on apache (>= 2.2)? any package that might take advantage of any number of features in apache2.2 not in apache2.0... there's a list here: http://httpd.apache.org/docs/2.2/new_features_2_2.html also, according to the report in bug 340770, that bug was fixed in apache2 2.2.3-1, but upgrading apache2 doesn't actually do anything, the version reported as having the fix doesn't actually have a fix, since installing this version doesn't do anything. --Jayen
