= Orchard autopkg Override Standards =
* Unless overriding for specific reasons (e.g. to get a broken download working) all Input keys/values you are not overriding relating to a URL (DOWNLOAD_URL, SPARKLE_FEED_URL etc.) should be removed, in case this changes in the parent recipe.
* {{{Identifier}}} should be in the format local.. (this is the default when using {{{autopkg make-override}}}
* {{{NAME}}} should be the name of the app with spaces expressed as underscores.
* {{{MUNKI_REPO_SUBDIR}}} should be set to {{{%NAME%}}} (except when grouping logical collections of apps e.g. Adobe Creative Cloud or MS Office installer and its updates in which case it should be {{{Name_Of_Collection}}}
* {{{MUNKI_CATEGORY}}} - if it exists - should have its string value set to one of the categories listed [[Infrastructure/Munki/Categories|here]]
* For the {{{pkginfo}}} dict that autopkg passes to munki:
* Change the string value of the {{{catalogs}}} to unstable. New applications should always go into the unstable Munki catalog at first. After they have been running for a while, this can be changed to stage directly to testing.
* If you have not set MUNKI_CATEGORY you should set it here with e.g.:
{{{
...
category
Design and Media
...
}}}
* If it's missing, add a {{{description}}} and a string value describing the app (this will appear to users in the Orchard Software Centre)
* If {{{display_name}}} is set to {{{%NAME%}}} and you changed the value of {{{NAME}}} above, you will doubtless want to change this to a more readable display name for users.
* Scripts to be run by munki when installing/removing this app should be added to the pkginfo dict. Create a {{{preinstall_script}}} or {{{postinstall_script}}} and add the HTML escaped script inside the corresponding {{{}}} tags.
* The command {{{$ sed 's/&(?!amp;)/\&/g; s/\</g; s/>/\>/g;' }}} is very useful for escaping scripts on the command line.