[suggest] Clamav should not require a specific clamav-db version

[Andreas Rogge]

Dag Wieers schrieb:

 > Imagine doing an condrestart behind the back but the service trips on
 > a configuration change from the past although the service was not
 > restarted for a long time. I think we are providing a bad service if
 > for that reason the service is down and may not be noticed until
 > complaints come in...
 >
> Although until now all RPM packages send output to /dev/null, my opinion 
> is that we should show it. (Except maybe when you do an uninstall, which 
> implies that you stop the service anyway)
> 
> What do you think ?

I don't know where I read it, but somebody proposed not to output 
anything on rpm operations.
The problem is that you never know where your output will actually go. 
For example, if you use yum-updatesd, you will probably never see that 
output.

IMO people should know that services will be restarted on an upgrade, 
simply because that's the way it works.

For your example: if a service is misconfigured and it then breaks on an 
upgrade, I don't think it is a problem with the rpm, but a problem with 
the admin. If one really wants to catch such an issue, you'd have to 
write a pre-script that checks wheter the configuration is ok and stops 
the upgrade otherwise.
However, that solution doesn't really look good to me. So what we have 
currently should probably be enough.

Regards,
Andreas

-- 
Solvention
Egermannstr. 6-8
53359 Rheinbach

Tel: +49 2226 158179-0
Fax: +49 2226 158179-9

http://www.solvention.de
mailto:info at solvention.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3303 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.rpmforge.net/pipermail/suggest/attachments/20080228/3405c8d1/smime.bin