Manifests are PowerShell scripts containing application information and their installation and uninstallation procedures. They have .ps1 extension. Manifests are recognized by denget as applications that it can install.
After doing some preparation work, denget will call this script with a command it should follow - install or uninstall. The rest is handled by the manifest.
In case of install script, its usual work is to check the availability of anything needed to install, download files from a source, install or unpack them, do any pre- / post-installation work, create shortcuts and clean after itself. For uninstall, it is to call uninstaller or delete files, remove shortcuts if any were created, and do any pre- / post-uninstallation work.
Manifests are strictly structured and unified to preserve readability and compatibility. They consist of sections, some of which are optional, and some are found in all manifests.
Detailed descriptions of each section are available in Creating an app manifest guide, covering all the details of manifests variables, data setup, installation/uninstallation steps and sections optionality. Here you will only find a quick overview.
Most of the sections look the same and may differ in file extensions or some extra steps here and there. Mainly, manifests for apps of the same kind, like those downloaded from GitHub or using the same installer (like GOG games), will look almost identical.
Each section is visually divided by a comment in format ### <SECTIONNAME> ###.
Toggle the section title to see its description.
### <APPSOURCE> <PORTABILITY> MANIFEST ###### PATH RESOLVER ###### DATA SETUP ###### NON-PORTABLE WARNING ###### SOURCE/RCLONE/ARIA2 RESOLVER ###