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?
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. any package having a dependency on a version of apache2 would get
tripped up because apache2 would destroy the version requirement. so then any
package depending on apache2 (>=2.2) should now depend on apache2-mpm-worker
(>= 2.2) | apache2-mpm-prefork (>= 2.2) | apache2-mpm-event (>= 2.2)? this
seems really wasteful and maybe you should remove the apache2 package to avoid
confusion.
--Jayen
----- Original Message ----
From: Tollef Fog Heen <[EMAIL PROTECTED]>
To: Jayen Ashar <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Sent: Sunday, October 22, 2006 11:09:24 AM
Subject: Re: Bug#394658: doesn't depend on correct versions
severity 394658 wishlist
tags 394658 + wontfix
kthxbye
* Jayen Ashar
| I think there is a need for an exact dependency. I upgraded from
| apache2 2.0.55-4.1 to apache2 2.2.3-2 and it didn't do anything.
| Nothing REAL got upgraded. My copy of apache2-mpm-prefork stayed at
| version 2.0.55-4.1.
Yes, and? This isn't a bug, there is nothing in apache2's description
which says «this ensures you have the latest version of all apache2
packages installed», and there shouldn't either. Dependencies should
be as loose as possible, but no looser.
--
Tollef Fog Heen ,''`.
UNIX is user friendly, it's just picky about who its friends are : :' :
`. `'
`-
