Currently, RR skips a pkg recipe if the download recipe already downloads a pkg installer.
Certain recipe types (e.g. jamf recipes) expect their parent to be pkg, so it's helpful to have a pkg recipe, even if it doesn't do anything. Additionally, even if the downloaded format is pkg, the naming convention of the file may not be the standard NAME-version.pkg that imports well into systems like Munki and Jamf.
Therefore it would be beneficial for Recipe Robot to build a pkg recipe with a single PkgCopier step if the download recipe downloads a pkg file, rather than skipping the pkg step.
Currently, RR skips a pkg recipe if the download recipe already downloads a pkg installer.
Certain recipe types (e.g. jamf recipes) expect their parent to be pkg, so it's helpful to have a pkg recipe, even if it doesn't do anything. Additionally, even if the downloaded format is pkg, the naming convention of the file may not be the standard NAME-version.pkg that imports well into systems like Munki and Jamf.
Therefore it would be beneficial for Recipe Robot to build a pkg recipe with a single PkgCopier step if the download recipe downloads a pkg file, rather than skipping the pkg step.