partly related: Item1556

---

I have also noticed all the .bak files everywhere. One of the reasons I personally have stopped using configure to install extensions. It leaves a mess behind of .bak files and installer files in the foswiki root.

-- KennethLavrsen - 17 May 2009

currently:

installation via configure leaves cruft lying about. specifically, this list of files:

• *Plugin_installer
• *Plugin.tgz (or .zip)?
• .bak files for each file listed in MANIFEST
  • .bak.bak (ad infinitum) files

---

proposed:

during installation, a .bak file should only be created if the file being written and the file already on disk differ

• current algorithm of appending .bak to be retained

at the end of installation, the following files should be deleted:

• *Plugin_installer
• *Plugin.tgz (or .zip)?

note that if the installation "fails" (meaning what?), then those 2 files will be left on disk.

-- WillNorris - 17 May 2009

Makes sense. .bak.bak is probably overkill, too.

-- CrawfordCurrie - 18 May 2009

Agree on Will's spec

-- KennethLavrsen - 18 May 2009

this is made obsolete by the much more ambitious ImproveExtensionBackupProcess.

-- WillNorris - 18 Mar 2010