It goes like this: * mysql database support in your USE flags. * sqlite database support in your USE flags. * You have multiple database backends active in your USE flags. * Will default to MySQL as your dspam database backend. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * If you want to build with another database backend; hit Control-C now. * Change your USE flag -mysql and emerge again. * It would be best practice to add the set of USE flags that you use for this * package to the file: /etc/portage/package.use. Example: * `echo "mail-filter/dspam -mysql postgres -oci8 -sqlite -sqlite3" >> /etc/portage/package.use` * to build dspam with Postgres database as your dspam backend. uid=26(dspam) gid=408(dspam) groups=408(dspam) uid=26(dspam) gid=408(dspam) groups=408(dspam) >>> Unpacking source... >>> Unpacking dspam-3.6.2.tar.gz to /var/tmp/portage/dspam-3.6.2/work >>> Unpacking dspam_sa_trainer.tar.gz to /var/tmp/portage/dspam-3.6.2/work >>> Source unpacked. * econf: updating dspam-3.6.2/config.guess with /usr/share/gnuconfig/config.guess * econf: updating dspam-3.6.2/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-long-username --with-delivery-agent=/usr/bin/procmail --enable-domain-scale --with-dspam-home=/var/spool/dspam --sysconfdir=/etc/mail/dspam --with-storage-driver=sqlite_drv --enable-virtual-users --build=i686-pc-linux-gnu ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ So it says it will use mysql and then uses sqlite, obviously totally breaking the whole dspam setup during upgrade (I believe this behaviour is different from previous versions, but I'm not sure - it just worked before but I can't say if I didn't add sqlite to common USE flags later).
Is this still a problem? I have mine running with sqlite3.
takeover the maintainership from st_lim.
dspam-3.6.8 tell no lie
