during installation. The additional metadata files, located under the special directory within the tarball, usually include a file, which is a specifically formatted text file that is read by the package manager to provide users with a description of the packaged software, as well as a file, which is a post-unpacking shell script allowing creation of symbolic links, preserving permissions on startup files, proper handling of new configuration files, and any other aspects of installation that can't be implemented via the package's directory structure. During the development of 15.0, Volkerding introduced support for a uninstall script that can be launched when removing or upgrading a package. This allows package maintainers to run commands when a package is uninstalled. The package manager maintains a local database on the computer, stored in multiple folders. On 14.2 and older systems, the main database of installed packages was maintained in , however, during the development of 15.0, Volkerding moved two of the directories to a dedicated location under to prevent accidental deletion when clearing system logs. Each Slackware installation will contain a and directory in the main database location. The former is where each package installed will have a corresponding install log file (based on the package name, version, arch, and build) that contains the package size, both compressed and uncompressed, the software description, and the full path of all files that were installed. If the package contained an optional post-installation script, the contents of that script will be added to a file in the directory matching the filename of the corresponding package in the directory, allowing the administrator to view the post-installation script at a future point. When a package is removed or upgraded, the old install logs and scripts found under and are moved to and , making it possible to review any previous packages and see when they were removed. These directories can be found in on 14.2 and earlier, but were moved to during the development of 15.0. On systems supporting the uninstall script, those scripts will be stored in the directory while the package is installed. Once removed, the script will be moved to . Dependency resolution The package management system does not track or manage dependencies; however, when performing the recommended full install, all dependencies of the stock packages are met. For custom installations or 3rd-party packages, Slackware relies on the user to ensure that the system has