On Tue, Mar 02, 2004 at 10:36:45AM +0100, Andreas Barth wrote:
> > exim4's existing dependencies are broken, because its expressing a
> > dependency on exim4 by listing conflicts for every package you could have
> > installed instead of it. If exim4-config doesn't need exim4 installed to
> > be usefully functional, it doesn't need to conflict with other m-t-a's,
> > if it does need exim4 installed it should be using a dependency.
> The same happens with libraries needed by a program.
No it's not, because those libraries don't need to be removed when
new libraries are installed. That's not the case with exim4-config,
apparently. (And if it is the case, we can handle it exactly as we handle
libraries, with no policy change required)
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
Linux.conf.au 2004 -- Because we could.
http://conf.linux.org.au/ -- Jan 12-17, 2004
Attachment:
signature.asc
Description: Digital signature