Bug#402721: Please make clear, that "conflicts" should only be used when really necessary
Russ Allbery <rra@debian.org> writes:
> Tobias Frost <tobi@frost.de> writes:
>> Looking at #262257, as an exampple, there are packages which declares
>> conflicts for whatever reason. However, the reason is NOT, that thec
>> packages could not co-existent on the same system (For the example,
>> retchmail could be also installed with fetchmail -- they do not
>> interfere)
>> My wishlist-entry would be to clarify, tha conflicts should only be
>> used, if the packages "won't do" if both installed... (as the word
>> "conflict" implies. The reason "the other package is doing the same, so
>> conflict on it to prevent both installed" is -- IMHO -- not the
>> intention of conflicts
> This really should be common sense, but it doesn't hurt to say it
> explicitly, which I don't think we were doing before. Here's a patch
> that implements that.
I've now merged this change for the next release.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: