P4
jpackage creates .jpackage.xml and .package files in app image.
.jpackage.xml file stores details of an app image needed in two-phase packaging on all platforms.
.package file stores the package name and is used by app launchers on Windows and macOS platforms to detect if the launcher belongs to the app image or installed package. In the latter case, it tries to read the launcher configuration file from the user's home directory.
.jpackage.xml file is supposed to be never found in native packages (msi, rpm, dmg, etc). But on macOS in two-phase packaging, it is added to DMG/PKG file if the input app image is signed. It can be deleted to keep the signature of the input app image solvent.
There is "Info.plist" file in the "Contents" directory of app image that can be used to store arbitrary data on macOS. It makes sense to store information from .jpackage.xml and .package files in the "Info.plist" file instead of these files. This will solve the problem of having .jpackage.xml in DMG/PKG files and reduce the number of files in the package.
.jpackage.xml file stores details of an app image needed in two-phase packaging on all platforms.
.package file stores the package name and is used by app launchers on Windows and macOS platforms to detect if the launcher belongs to the app image or installed package. In the latter case, it tries to read the launcher configuration file from the user's home directory.
.jpackage.xml file is supposed to be never found in native packages (msi, rpm, dmg, etc). But on macOS in two-phase packaging, it is added to DMG/PKG file if the input app image is signed. It can be deleted to keep the signature of the input app image solvent.
There is "Info.plist" file in the "Contents" directory of app image that can be used to store arbitrary data on macOS. It makes sense to store information from .jpackage.xml and .package files in the "Info.plist" file instead of these files. This will solve the problem of having .jpackage.xml in DMG/PKG files and reduce the number of files in the package.