On Tue, Jul 16, 2002 at 05:04:56PM -0400, Sam Varshavchik wrote: > Ben Rosengart writes: > > >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? > > It reminds me of a quote I've heard a long time ago, regarding the federal > budget appropriations process in Washington, DC: "A billion here, a billion > there, and pretty soon you'll be talking real money."
This is a five-line patch, not counting whitespace. The feature is easy to test; I can supply a test program suitable for a regression suite if you like. > >>Existing facilities already handle the situation adequately. > > > >How? Unless I misunderstand the directory mechanism, neither of the > >methods you've suggested is adequate. > > I do not really remember your particular details. Simple: we generate a userdb on host A, in /export/foo. We read it on host B, in /foo. Please do not suggest that we maintain two builds of courier-imap. I don't think you would appreciate it if someone treated you as if your time had no value, so please don't do the same to me. -- 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 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
