Aaron Stone wrote:

Looks good. I got my OS X info from the ltdl documentation; it's likely that
it isn't 100% up to date with their code in CVS. I'd say include it into the
source tree, but possibly in a subdirectory someplace (like dbmail/ltdl/).

Don't forget that it's not just the 'backend' -- there's also the auth-sql
split, and sorting to worry about. Not a big deal, something like:

AUTH_TYPE = [sql, ldap]
DB_TYPE = [mysql, pgsql, oracle]

My ODBC driver is almost done, I'll include that too. I told Paul that I thought it was most important I get the backends up and running first. Ill take the others on as soon as I can. For the sort stuff, I can't see any reason why to split that, its either you have sieve or not. I suspect the general concensus would say have sieve, and that the standard sort would probably be unused. It really comes down to whatever makes sense.

It would make sense to have full-path-to-library option as you've suggested,
but only as a sort of "expert mode." For the general case, DBMail should
figure that out by itself using just a this-or-that type option.

I'll set the standard location ${prefix}/lib/dbmail. That is pretty trivial.

Aaron
Dan Weber

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to