Currently, the recipes are displayed in this order:
[ ] 0. filewave - Imports a fileset into your FileWave server.
[ ] 1. munki - Imports into your Munki repository.
[ ] 2. install - Installs the app on the computer running AutoPkg.
[ ] 3. jss - Imports into your Casper JSS and creates necessary groups, policies, etc.
[ ] 4. download - Downloads an app in whatever format the developer provides.
[ ] 5. absolute - Imports into your Absolute Manage server.
[ ] 6. ds - Imports into your DeployStudio Packages folder.
[ ] 7. sccm - Creates a cmmac package for deploying via Microsoft SCCM.
[ ] 8. pkg - Creates a standard pkg installer file.
I think they should be displayed in this order, based in part on the ParentRecipe chain and in part on popularity.
[ ] 0. download - Downloads an app in whatever format the developer provides.
[ ] 1. pkg - Creates a standard pkg installer file.
[ ] 2. munki - Imports into your Munki repository.
[ ] 3. install - Installs the app on the computer running AutoPkg.
[ ] 4. jss - Imports into your Casper JSS and creates necessary groups, policies, etc.
[ ] 5. ds - Imports into your DeployStudio Packages folder.
[ ] 6. absolute - Imports into your Absolute Manage server.
[ ] 7. filewave - Imports a fileset into your FileWave server.
[ ] 8. sccm - Creates a cmmac package for deploying via Microsoft SCCM.
Currently, the recipes are displayed in this order:
I think they should be displayed in this order, based in part on the ParentRecipe chain and in part on popularity.