Holger Levsen wrote: >> MySQMail needs an SQL connection to the database of DTC. It is expecting >> that DTC is setup fully, as well as it's database, with granted access >> rights. The issue is that DTC can't set it up at postinst stage, because >> there would be all sorts of policy violations, as a package can't change >> another package conf file, wich it needs to. So things are done with a >> userland script that the user need to start to finish the installation. >> This is what mysqmail depends on!!! > > So it seems mysqmail cannot work out of the box, but needs manual > configuration. That's the case for quite some package. Also, mysqmail is a > logging system for qmail (and ftp server, but not for other mailers, right?) > and qmail isn't in Debian, so the user will have to do manual work anyway, so > that shouldnt be that big deal.
It USED to be for qmail only. Now it's NOT for qmail anymore, it's for: - pure-ftpd - postfix - courier - dovecot I have dropped the support for qmail because not in Debian. However, the situation might change as Qmail is not in public domain, and the (new) upstream author reportedly in the Debian BTS is working on the deffered bounce issue. I don't know the status of this change, but that is currently a blocker to have Qmail included in main (a vote decided that qmail is not a good enough netizen until this is fixed was sent to the BTS). The source code for logging qmail logs is still in the source of the mysqmail package, but there is no mysqmail-qmail package anymore. >> Now, give me the solution to this unsolvable issue and I will be very happy >> to send a fix to the archive. > > Make the package install cleanly and inform the user that it needs manual > configuration. I saw your package doesnt have a README.Debian, I think it > should have one. (Also docs/README doesnt mention how to configure dtc.) What about if I just exit 0 with a warning message if the relevant files the setup script expect, and ask to dpkg-reconfigure if DTC if finished to be configured? That would solve all... >>> So it's better to violate policy and break assumptions which are valid >>> for 25000 other binary packages? I don't think so. A package needs to >>> install cleanly, even if the moon is in a bad phase. >> Truth. But I'm unsure if there is a way to cleanly fix here without adding >> hasle for the users, which I don't want to... > > Well, the user has the "hassle" anyway, as she has to configure dtc no matter > what. Now, additionally your package fails to install if this hasnt been > done. So the current situation is more hassle, not less. I'll write a README.Debian as you said. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
