|| Perhaps a possible course of action is to offer several dovecot-auth
|| packages, with a default dovecot-auth-filesystem or whatever that uses
|| the basic password auth, and then other dovecot-
|| auth-{pgsql,mysql,ldap,...}. Then, there would be dovecot-auth-full for
|| those who need several of those installed at the same time.
| In order to save about 3MB of disk space? I don't see any point in
| the maintenance overhead.
Well, I just don't like having unneeded stuff around.
|| I see it kind-of-like the apache2-mpm-worker and apache2-mpm-prefork,
|| when one is installed, it uninstalls the other, etc. I don't know if
|| this kind of packages are common, but I know that I would love to have
|| them without having to manually recompile the src.
| -mpm-worker and -mpm-prefork are not possible to combine into one
| package in any sane way and have very different performance and
| feature characteristics, so the comparison doesn't hold.
|
| In general, the policy is for packages to be compiled with all
| features enabled rather than being able to turn features on and off.
| The one big exception to this is X support where quite a few packages
| exists both with and without X support.
Well.. what a pity then! :-/ Thanks for the explanation.
* "J. Javier Maestro"
|| Perhaps a possible course of action is to offer several dovecot-auth auth-filesystem or whatever that uses mysql,ldap, ...}. Then, there would be dovecot-auth-full for
|| packages, with a default dovecot-
|| the basic password auth, and then other dovecot-
|| auth-{pgsql,
|| those who need several of those installed at the same time.
| In order to save about 3MB of disk space? I don't see any point in
| the maintenance overhead.
Well, I just don't like having unneeded stuff around.
|| I see it kind-of-like the apache2-mpm-worker and apache2- mpm-prefork,
|| when one is installed, it uninstalls the other, etc. I don't know if
|| this kind of packages are common, but I know that I would love to have
|| them without having to manually recompile the src.
| -mpm-worker and -mpm-prefork are not possible to combine into one
| package in any sane way and have very different performance and
| feature characteristics, so the comparison doesn't hold.
|
| In general, the policy is for packages to be compiled with all
| features enabled rather than being able to turn features on and off.
| The one big exception to this is X support where quite a few packages
| exists both with and without X support.
Well.. what a pity then! :-/ Thanks for the explanation.
Cheers