Created attachment 328344 [details] compressed build log * package mail-mta/courier-0.69.0 NOT merged * * Detected file collision(s): * * /usr/share/man/man1/dot-forward.1 * /usr/bin/addcr * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-apps/ucspi-tcp-0.88-r17 * /usr/bin/addcr * * net-mail/dot-forward-0.71-r3 * /usr/share/man/man1/dot-forward.1
for dot-forward it probably doesn't make much sense to have qmail-related tools on a courier-system, so maybe we should just add a blocker. For addcr I'm unsure, seems both packages provide the same tool. But it's also related to qmail, so maybe also just block it?
!sys-apps/ucspi-tcp and !net-mail/dot-forward in the ebuild looks fine for me. I'll apply the changes if I don't get any response in 30 days.
Done.
*** Bug 491670 has been marked as a duplicate of this bug. ***
The !sys-apps/ucspi-tcp dependency means courier and djbdns can't be installed simultaneously, and since they're commonly used together this is a problem. Since addcr is such a simply utility and since /usr/bin/addcr installed by courier is a symlink to /usr/lib64/courier/courier/modules/esmtp/addcr on my system, could the symlink not be avoided during courier's install if it's already present, but the file in /usr/lib* still be installed? I expect ucspi-tcp would need a similar modification. What is the normal process to fix this kind of issue? Adding a addcr-config or eselect module seems a bit excessive.
