mail-mta/courier comes with its own version of maildrop. This is overwritten by the mail- filter/maildrop and could cause courier to stop working. Therefore I think that mail-filter/ maildrop should check for mail-mta/courier before installing. Reproducible: Always Steps to Reproduce:
Does it come from the same source-package? if so, courier should not install that file, but use maildrop instead. If not, yes, they should conflict (sandbox violation)
(In reply to comment #1) > Does it come from the same source-package? if so, courier should not install > that file, but use maildrop instead. > > If not, yes, they should conflict (sandbox violation) I am not sure what you mean. If you mean they use the same source files, then no: maildrop-1.8.0.tar.bz2: 2 013 203 bytres courier-0.48.1.tar.bz2: 5 875 035 bytes I did test to install maildrop. It broke courier (it could not deliver through the new maildrop). Possible explaination is that the new maildrop uses different config files than couriers' maildrop.
You said courier should not install that file. Yes, if it was the same maildrop, then would it not be better to have a dependency on maildrop?
mail-mta/courier uses an internal copy of maildrop which isn't exactly the same as the released version of maildrop. I can add a blocker in courier for maildrop, but I think maildrop should do the same just to be safe.
It's probably better to move courier's maildrop away so both won't collide. Anyway... I don't mind blocking courier from maildrop. Cheers, Ferdy
Ok, blocked courier from maildrop in maildrop-1.8.1-r1.ebuild Cheers, Ferdy
