backup systems. (Use Amanda!!)

[jabr at abreau.net (John Abreau)]

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

Derek Atkins <warlord at MIT.EDU> writes:

> Not really.  For example one time I submitted a patch to an
> RPM-installed file (which was later accepted).  I planned to upgrade
> the RPM anyways once the patch was accepted, but didn't want to put
> the system in a state where the upgrade would fail.
> 
> Also, not all modified files are necessarily executables -- sometimes
> they are ancillary scripts, configuration data, etc -- and those
> locations are hard-coded into existing binaries.  Are you suggesting I
> mv the file and replace it with a symlink?  That would be just as
> problematic (if not moreso).

It sounds like you're talking about a pathological case that's unusual 
and temporary. An admittedly non-robust approach for dealing with this 
would be a manually-maintained inclusion list, and developing a habit of 
updating it whenever you need to mess with an rpm-installed file in 
that manner. 

It's ugly, to be sure, but then so is the idea of modifying an 
rpm-installed binary.


- --
John Abreau / Executive Director, Boston Linux & Unix
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.6 02/09/2003

iQCVAwUBPpdVUlV9A5rVx7XZAQLHiAQAo3mNltDG+0GhXmsMjeVTJn60Xu9D58Us
bmkZ6kjN5/qKp+zkmU4+TQT3MXI1VODLynE/L5A7ASCMYGqgary8QN+xjEb8O2YR
NG8GzFfC4B72MPsHyZfYJqsxPOcu8S0ilgMX1KvpAK3mTC9L+RPNVgwXJx/PKvd4
ZCfv1JVxTyE=
=/b6U
-----END PGP SIGNATURE-----