Contents
What does a postinst script do in Debian?
This script typically completes any required configuration of the package foo once foo has been unpacked from its Debian archive (“.deb”) file. Often, ‘postinst’ scripts ask the user for input, and/or warn the user that if he accepts default values, he should remember to go back and re-configure that package as the situation warrants.
Where do I find package Foo in Debian?
The files relevant to package foo begin with the name “foo” and have file extensions of “preinst”, “postinst”, etc., as appropriate. The file foo.list in that directory lists all of the files that were installed with the package foo. (Note that the location of these files is a dpkg internal; you should not rely on it.)
Where do I find control files in Debian?
Currently all of the control files can be found in directory /var/lib/dpkg/info. The files relevant to package foo begin with the name “foo” and have file extensions of “preinst”, “postinst”, etc., as appropriate. The file foo.list in that directory lists all of the files that were installed with the package foo.
What happens if I uninstall postrm in Debian?
Your postrm deletes log files, and files inside the uninstalling user’s home directory (assuming it’s uninstalled using sudo ); both of these are definite no-nos, home directories are off-limits for maintainer scripts, and logs should be left behind on removal (and purge).
Where can I find postrm file in Debian?
A package can perform several post-removal actions via maintainer scripts, by including an executable postrm file in its control archive (i.e. DEBIAN/postrm during package creation).
What is a preinst, postrm, and postrm script?
6.6 What is a Debian preinst, postinst, prerm, and postrm script? These files are executable scripts which are automatically run before or after a package is installed. Along with a file named control, all of these files are part of the “control” section of a Debian archive file.
Why is my postinst script not being run with install?
I checked that /etc/default/myapp does not exist. The file /var/lib/dpkg/info/myapp.postinst exists, and if I run it manually with install as the first parameter, it works as expected. Why is the postinst script not being run with install?