- Blockblock autopkg recipe install#
- Blockblock autopkg recipe series#
- Blockblock autopkg recipe download#
- Blockblock autopkg recipe mac#
This will run through the recipe and display the output of each processor. Now you have your list all you need to do is enter the following into Terminal: "autopkg run –v " If you don’t get any results, it’s probably that you missed the ‘repo-add’ step on the wiki. This should give you a list of the recipes available on your Mac: Fire up Terminal and enter “autopkg list-recipes” and press ‘return’. The first thing you’ll need to do is to find out what recipes you have locally on your Mac. Now let’s take a brief look at the usage of AutoPKG. Right, so you have a little understanding of the overall installation and setup and you have configured your AutoPKG as per the wiki page. The default is blank and an example would be “/Volumes/DataHD/munki_repo”. If set, and if a “.munki” recipe is run, then AutoPKG will automatically add the item into Munki as part of the ‘run’.
“CACHE_DIR” – This is a string value to denote where to store the finished output files.These all go into the “” preference domain. The AutoPKG wiki also details a lot of preferences you can use with AutoPKG. Once complete, recheck and you should get the Git help output.
Blockblock autopkg recipe install#
Otherwise, you’ll see the following output, with a Software update popup:įollow the onscreen instructions to install the Xcode tools. If you already have the tools installed, you’ll see a help page for git:
Blockblock autopkg recipe download#
If you’re running Mavericks, the simplest way to check if you have this installed (and to download it otherwise) is to launch terminal, enter ‘git’ and press return.
One of the requirements for the AutoPKG is the Git command line tool that is used to pull down recipes. Rather than repeat that pretty great step-by-step guide, I’ll just point out a few gotchas and good-to-know areas. The best guide to the installation of AutoPKG can be found on their wiki. The result of this methodology is to make the solution highly modular to make fixes and upgrades easier to implement.įor further information, check out the wiki (under the Processors and Recipes headings). Recipes are XML formatted files that detail the inputs for the item and which processors to use and pass the information between.
Blockblock autopkg recipe series#
The idea behind this is that to download, tweak and package a piece of software, a few inputs are fed into a series of processors that will pass files and further inputs to each other to result in the final product. For example, AutoPKG includes a ‘URLDownloader’ processor that will take an input of a URL and download what it finds. Processors are small but highly specialised modules created to run a specific task.
Blockblock autopkg recipe mac#
The tool itself is very simple to install and use and if you are responsible for managing a Mac environment, I can’t recommend it enough! Recipes and ProcessorsĪutoPKG relies on two items to operate recipes and processors. Additionally, tools have been provided to allow other user to contribute to the recipes, increasing the number of software that can be dealt with in this way.”
Co-developed by Tim Sutton and Greg Neagle (two of the heavy-weights in Mac Admin’ing) it’s a great tool that, with the usage of recipes, can automatically download the latest version of software, perform some basic to intermediate repackaging, and automatically add the results into Munki Repo/s.Īs it’s command-line based, it can be scripted and scheduled, allow certain mundane packaging tasks to be fully automated. “AutoPKG is a relative new kid on the block in the Mac Admin world. I’m going to cheat and use my blurb from the last blog: Hi all, this month I’ve decided to go over one of the tools I’ve mentioned in my previous blog AutoPKG.