Windows installer leaves obsolete utility scripts behind

[Brian Smith]

Early versions of POPFile often included some extra utility scripts written in Perl. The Windows installer has always ignored these files even though they may no longer be of any use. In fact some of these scripts may no longer be safe to use!

The installer cannot simply delete all the files with matching names because, for example, the file 'test.pl' may not in fact have been shipped with POPFile.

Perhaps the installer should use MD5 checksums to confirm the identity of these obsolete scripts and rename them by adding '.obsolete' to the end, e.g. 'test.pl.obsolete', instead of permanently deleting them?

Here is a list of the scripts involved:

Script	POPFile releases
autotest.pl	0.17.3, 0.17.4, 0.17.5, 0.17.6, 0.17.7, 0.17.8, 0.17.9a
bayed.pl	0.18.2, 0.18.3
color.pl	0.17.3, 0.17.4, 0.17.5, 0.17.6, 0.17.7, 0.17.8, 0.17.9a, 0.18.0, 0.18.1, 0.18.2, 0.18.3
hash.pl	0.17.3, 0.17.4, 0.17.5, 0.17.6, 0.17.7, 0.17.8, 0.17.9a, 0.18.0, 0.18.1
hist.pl	0.18.0, 0.18.1
pfdiagnose.pl	0.18.1
r.pl	0.18.1
search.pl	0.18.0, 0.18.1
speed.pl	0.18.0, 0.18.1
temp.pl	0.18.0, 0.18.1
test.pl	0.17.4, 0.17.5, 0.17.6, 0.17.7, 0.17.8, 0.17.9a, 0.18.0, 0.18.1
testin.pl	0.18.2, 0.18.3
tests.pl	0.18.0, 0.18.1, 0.18.2, 0.18.3
ui.pl	0.17.7, 0.17.8, 0.17.9a
viewer.pl	0.17.3, 0.17.4, 0.17.5, 0.17.6, 0.17.7, 0.17.8, 0.17.9a, 0.18.0, 0.18.1, 0.18.2, 0.18.3
words.pl	0.18.2, 0.18.3

There are 16 scripts in that list but I have not examined any of them yet.

[Brian Smith]

The Windows installer already does some tidying up of obsolete files (mainly executables) but in an ad hoc fashion. Perhaps it is time to create a new "clean up" function based upon the current scattered code fragments and new code to handle these obsolete Perl scripts?