|
| Just a ping to see what you want to do with this. I feel that it is not
| necessary to add to debconf, as it has a sensible default for most
| systems. In the event that you are running clamd on a severely disk
| constrained system, this option can be added manually, and it will be
| preserved over upgrade. I feel that the option is satisfactorily
| explained in the man page as well.
Yes, the behavior of 0 is explained there. The confusion arose, when
it was explicitly set. I waould have expected the manual page's
default value. Thus the question: "Why the defaul configuration uses
0?"
| I am inclined towards closing, but I am not going to do so if you
| disagree. Please let me know what parts are still unclear, and maybe we
| can come to some consensus about it. If in the end we still disagree, I
| will downgrade the severity to wishlist and leave it open for a future
| maintainer to handle if they see fit.
I took a quick look at clamav-daemon.postinst lines:
213 echo "#Automatically Generated by clamav-daemon postinst" >
$DEBCONFFILE
214 echo "#To reconfigure clamd run #dpkg-reconfigure clamav-daemon" >>
$DEBC
Would it be possible to one more comment line to this section to
shortly refer to the reasons the value is 0. That would really help
from my part in this issue.
Other than that, I do not have expertise on how the upgrade works, or
how the confguration files are managed, so I'm unable to make better
suggestions.
Jari
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
