On Fri, Jul 05, 2002 at 11:59:49PM -0400, Sam Varshavchik wrote:
On Fri, Jul 05, 2002 at 11:51:01PM -0400, Ben Rosengart wrote:
We don't build the userdb on the same host where we use it.
You have a site-specific custom configuration.
The destination directory can currently be set at compile time.
I am proposing making this configurable at run-time too. What is
the down-side? Who could possibly be harmed by making the software
slightly more flexible?
We could use the symlink trick, but what happens when we want to
have a couple of different courier-imap installations with different
Create different symlinks.
Can you explain exactly how this would work?
Remember: the goal here is to be able to generate distinct userdbs
from distinct source files on the same host.
Existing facilities already handle the situation adequately.
How? Unless I misunderstand the directory mechanism, neither of the
methods you've suggested is adequate.
Ben Rosengart (212) 741-4400 x215
Microsoft has argued that open source is bad for business, but you
have to ask, "Whose business? Theirs, or yours?" --Tim O'Reilly