| Summary: | courier authdaemon directory is not created [/or created with courier-imap directory instead] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Clemens Schwaighofer <gullevek> |
| Component: | Current packages | Assignee: | Brian Jackson (RETIRED) <iggy> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | grandmasterlinux, raphael, robbat2 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Clemens Schwaighofer
2003-07-21 21:12:06 UTC
courier and courier-imap should not be installed at the same time. courier contains courier-imap already. then, for gods sake, Block each other package. it should be possible to either block courier-imap from installing when courier is installed, or vica versa. if this is not possible, then this is either A) a very important feature for portage, or B) (more logical) imap functionallty has to be turned of in courier so courier and courier-imap are two seperate packages that complement each other. If you read the courier webpage you will notice that courier can be installed in separate parts. There are reasons for this. Sometimes courier-imap is used with other mta's. Maildrop (part of courier) can be installed to take the place of procmail. Or you can get the whole shebang with courier. Some people might want to install courier-imap and courier at the same time (i.e. for converting from courier-imap/ some-other-mta -> courier with only one box). While I do think we should attempt to make some things difficult to do, so inexperienced sys-admins don't shoot off their own toes, this is not one of them. if I download the source from the courier webpage and do it myself I can shoot myself int he foot. but if a linux distribution gives me two packages called courier and courier-imap, I first think (and I am sure I am not the only one), that courier is pop/smtp without imap and courier-imap is the imap adon. it is not so, good, then why don't you block each other package? shoudln't be too complicated. i vote having courier installed should block the standalone courier-imap/maildrop/etc and vice-versa. Maybe instead of blocking via DEPEND, through a function in pkg_setup which dies if it detects a conflicting Mr. Sam package already installed and informing the user of the problem and valid choices for a solution? Just a thought. What do you think iggy? I still think it's a bad idea to just block something like that. I've personally had to move from qmail/courier-imap -> courier back in my Slackware days, and if I had been unable to install both on the same system, I would have been SOL. I can do a conditional warning that says something along the lines of "you already have courier-imap installed, courier includes this functionality, so you should remove it unless you need it". Would that satisfy everybody? Maybe we could talk robbat2 into doing something similar. Iggy: doing that would break non-interactive emerges. Eg user does emerge -p ... and it all shows fine, then leave emerge ... running and comes back in the morning to find the second item, courier, stopped his entire list to emerges. I'm strongly with Nick on this one. A precedent for doing this already exists with MTAs anyway. try: emerge -p qmail sendmail Fine, done. added !virtual/imapd to RDEPEND the problem here isn't that courier-imap and courier get installed concurrently, but courier-imap's initscript not working if ONLY the courier-imapd is installed it just erroneously looks into /usr/lib/courier which simply doesn't exist (unless you install the courier package) moved the version that fixes this to x86 |
