Re: Tracking changes made by installation of software
jiri writes:
> Actually, a simple version shouldn't be difficult at all - if you start
> with the `find and diff' idea, but put a checksum next to each of the
> files, then you'll have a list of files added, files removed and files
> changed. For the changed files, you compare them with an archive version
> using diff again.
MallarJ writes:
> You're right, this isn't a major undertaking - just trying to prevent
> dupication of code that might already be in existence. The find and diff
> idea is the exact approach I plan on using.
What problem are you trying to solve here? You do realize that dpkg saves
a md5sum of every conffile it installs, don't you? And that when you
upgrade the package that dpkg will check the md5sum and, if it has changed,
ask your permission before overwriting the file?
--
John Hasler This posting is in the public domain.
john@dhh.gt.org Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisconsin Do not send email advertisements to this address.
Reply to: