Installwatch

Installwatch is a program designed to make it easier to catalog and maintain software installed from source code. Originally developed as a stand-alone project, Installwatch now exists primarily as a component of CheckInstall.

Installwatch
Original author(s)Pancrazio 'Ezio' de Mauro
Developer(s)Felipe Sánchez
Stable release
1.6.1 / November 1, 2006 (2006-11-01)
PlatformUnix-like
TypeSoftware management
LicenseGNU General Public License
Websiteasic-linux.com.mx/~izto/checkinstall/installwatch.html

Installwatch was originally written by Pancrazio 'Ezio' de Mauro in 1998, but development was later taken over by Felipe Sánchez.[1]

Functionality

Installwatch allows the user to monitor what files and directories are created during the installation of a software package in real-time. This allows the user to know exactly what has been installed on their system for the purposes of documentation and later removal of the software.[1]

When used on its own Installwatch is of limited usefulness, as it can only create a log of the installation process. Because of this, Felipe Sánchez created CheckInstall; which takes the information generated by Installwatch and uses it to create an installable package which can be used on any Linux distribution that makes use of Debian, Slackware, or Red Hat package management systems.

The use of CheckInstall has largely superseded that of Installwatch alone, and as such Installwatch has now been merged with the CheckInstall distribution. Older stand-alone versions of Installwatch still remain primarily for historical and educational purposes.

Coreutils incompatibility

At present, the version of Installwatch packaged with CheckInstall is incompatible with the current version of the GNU coreutils (Core Utilities). Because of this, Installwatch can't monitor any changes made with the coreutils, rendering its logs incomplete. Depending on the software package, this may completely invalidate the information provided by Installwatch and thus any program that depends on it (such as CheckInstall).

This issue was documented in the Slackware 12 changelog, and prompted CheckInstall's removal from that distribution.[2] On August 3, 2007, the problem was further explained and detailed by Felipe Sánchez on the CheckInstall mailing list.[3]

An updated version of CheckInstall is promised to be coming soon which will address the issue, and in the meantime a workaround is suggested.[4]

gollark: There's some weirdness where it's not *strictly* rolled back entirely so some information can be extracted through bizarre side channels.
gollark: Spectre/Meltdown work using weirdness in speculative execution, which is where the CPU executes stuff faster by assuming one possibility is true then rolling it back if it's wrong.
gollark: CPUs have a bunch of privilege separation mechanisms, but flaws in them sometimes get around those.
gollark: The general thing with these flaws is just that the CPU behaves in some way it shouldn't/isn't documented as doing, so information is leaked from places or stuff which shouldn't be changed is changed.
gollark: Or static analysis of some sort, but detecting malware without just banning tons of legitimate code is extremely hard and possibly impossible.

See also

References
  1. Sánchez, Felipe. "Installwatch Homepage". Retrieved 2007-07-23.
  2. Volkerding, Patrick (2007-07-19). "Slackware 12 Changelog". Retrieved 2007-07-23.
  3. Sánchez, Felipe (2007-08-03). "CheckInstall mailing list". Retrieved 2007-08-12.
  4. Sánchez, Felipe. "CheckInstall Homepage: Recent News". Retrieved 2007-08-12.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.