[users] selfupdating packages

[Todd Lyons]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Jul 25, 2007 at 12:18:19PM +0000, rance at frontiernet.net wrote:

> I have a question about the "proper" way to handle sofware that
> updates itself.

In RPMs, you design the spec file properly.  Going into a bit more
detail than the previous reply...

> when I issue a "yum update" from my centos box clamav-db gets
> installed as an update, but it is possible that the rpm update
> actually "undoes" any freshclam update to a newer version of the db
> than when the updated rpm was originally made.

No, the spec file looks like this:

%files db
%defattr(0644, clamav, clamav, 0755)
%config(noreplace) %verify(user group mode) %%{_localstatedir}/lib/clamav/

That may not mean a whole lot to you, but the above says that the
clamav-db package is designed to not overwrite any files in
/var/lib/clamav, which is where your database files live (or
/var/clamav, depending on which package builder you use).  It doesn't
throw them away either.  They get written as daily.cvd.rpmnew and
main.cvd.rpmnew.  The above rpm stanza is standard for clamav rpm
builds.
- -- 
Regards...		Todd
Chris: grep 500 sendmail.mc 
undefine(`FAIL_MAIL_OVER_500_MILES')dnl
Chris: just in case ...
Linux kernel 2.6.17-6mdv   2 users,  load average: 0.18, 0.12, 0.06
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGp2f9Y2VBGxIDMLwRArTCAJ9b6D//CgE41S9qnG/NW/me4NEmfQCfcWuW
qbO3yoC9FxZqD8isFblMvcQ=
=eYxe
-----END PGP SIGNATURE-----