Automated Software Packaging using AutoPkg

Software for OS X systems is packaged using the AutoPkg framework. AutoPkg is oriented towards the automation of the tasks one would normally perform manually to prepare third-party software for mass deployment. AutoPkg defines these tasks in a "Recipe", which can be defined in an understood (plist-based) format, run automatically instead of by hand, and shared with others. These Recipes can easily be shared and adapted to local requirements. For Orchard we utilise existing community recipes (or write our own) and enhance them to meet our specific requirements.

The majority of software packages created using AutoPkg are automatically added to the Orchard testing release and immediately available to early adopters in the Orchard Software Centre. These packages will eventually be staged to all managed OS X clients in the stable release.

Contributing to Orchard AutoPkg

• How to contribute

• Guidelines for overriding existing recipes for Orchard

• Guidelines for writing new recipes for Orchard

• How to create general purpose packages (e.g. for Software Licensing)

• Guidelines for writing package documentation for Orchard

• Checklist for Orchard Administrators to perform once recipes accepted

• Using Orchard VPN

TODO

• Describe automated build process
  • base info on build server
  • how often do we build?
  • yes, we are happy to accept patches and new recipes (with a link to our standards)
• Brief description of staging (with a link to a detailed page for Munki-Trello)
• Some references to munki?
• How do we list our software packages? Do we have a /AutoPkg/Recipes/ tree or a /Software/ tree (Marko prefers the latter)?

Further Reading

• AutoPkg Introduction

• AutoPkg Getting Started

CategoryWikiToDo