- #BLOCKBLOCK AUTOPKG RECIPE HOW TO#
- #BLOCKBLOCK AUTOPKG RECIPE FULL#
- #BLOCKBLOCK AUTOPKG RECIPE CODE#
- #BLOCKBLOCK AUTOPKG RECIPE DOWNLOAD#
Sidebar: While not applicable in this case, there is another variety of processor called a Shared Processor.
Often less efficient, code-wise (if you care about such things). May require extra steps to do the same thing as a custom processor does (if possible at all). Limited by what existing processors can do. If you can’t write Python and the custom processor requires an update, you have to wait for someone else to do it. Requires knowledge of Python or a good testing scheme to audit a custom processor for trust. Requires knowledge of Python to write a custom processor. Easier to audit recipes for trust (especially if you don’t know Python). #BLOCKBLOCK AUTOPKG RECIPE CODE#
Recipe author does not need to be able to code in Python.Processors are well-documented (including changes) and perform common tasks.Processors have already been vetted by hundreds of users.Allows addition of features not currently covered by core processors.Can be coded to use human-friendly Input values.
#BLOCKBLOCK AUTOPKG RECIPE DOWNLOAD#
Can deal with complex/unique download and/or versioning situations. So what are some of the advantages and disadvantages to using a custom processor over core processors (and vice versa)? The difference is that the core AutoPkg recipes use a custom-built processor to determine the download, and the arubdesu and rtrouton recipes use a core AutoPkg processor. They also do the right thing by inserting an EndOfCheckPhase processor in-between Steps 2 and 3 to properly handle running the recipe with the -c or -check option. The aforementioned recipes for Office all conform to that. Check the code signature of the downloaded item. Download a copy of the item (if we don’t have the current version in hand already). Determine the URI of the item we want to download. The most common workflow we would see in any download recipe is: So with those qualifiers out of the way, let’s look at how each set downloads the desired Office apps. (The remainder of that repo is a smörgåsbord of different techniques, sharing code in some cases with the core recipes.) Conversely, I’ve taken the rtrouton Office Suite recipes out of the mix because they are essentially rebranded arubdesu SKUless recipes the product-specific recipes have a unified approach that is different than the Suite and the core recipes. I am only referring to the SKUless recipes in the arubdesu/office-recipes (the ones designed to download the entire suite) because they offer an approach that is different than the other two major recipe sets and thus are useful for study. However, you may notice that I have added significant qualifiers this time when I specified which recipes are being referenced, primarily to keep the discussion tidier. In previous articles, I referred to these as the core, rtrouton, and arubdesu recipes respectively, so I will continue that usage here. 
The “SKUless” recipes in Allister Banks’ personal (non-project) GitHub repo.
#BLOCKBLOCK AUTOPKG RECIPE FULL#
Rich Trouton’s recipes, excluding the recipes for the full Office Suite.This post will look at downloading and gathering version information using both methods.Īs in previous Office recipe posts, I will refer to three different recipe solutions: The Microsoft Office sets of recipes, which I have written about in many previous posts, provide examples of how you can do the same task with a custom processor or without.
#BLOCKBLOCK AUTOPKG RECIPE HOW TO#
But sometimes you need something more - or, if you know how to write Python, you can see a much easier and/or elegant solution if you just write some code. Everyone who uses AutoPkg depends on them. The core AutoPkg processors pack a lot of punch.
0 kommentar(er)
