#Smarky mac update
# App Family Name, used to make title of Update News web page. # Path to Help Book HTML in built product, relative to the built productīuiltHelpPath Contents/Resources/English.lproj/HelpBook/index.html If this configuration is for the regular family, where the highest-numbered version is the latest version, set both values to 0. # The next two numbers are the major minor version numbers defining the limits for the family (regular, legacy, stone-age) etc., which will be used to identify the "previous" version when comparing the product's Contents to the "previous" version. # Name of dmg file which will appear on server. No need to quote anything since values are delimited by end of line or backslash (continued on next line) shipconfig.txt file which needs to be supplied as an argument to the script. Smarky.shipconfig, is a sample, well-commented configuration file whose path would be a parameter to. I can do anything I want in Perl and have not yet had an occasion to learn much of the shiny new scripting languages of the 21st century.
The trouble with these things is that everyone has their own way of doing it, but you can copy out the parts you want. The comment at the beginning lists dependencies on other tools, some of which are mine.
It will run you through a comprehensive quality-control checklist, supports alpha, beta and production channels, builds the product (or re-ships a previous build to a different channel), codesigns all components with Developer ID per Apple TN2206, builds the Help Book from Markdown sources, ships it, archives the product, updates Sparkle feeds, and much more, and also does a lot of automated quality control checks. This script is for shipping OS X apps outside the Mac App Store.
0 kommentar(er)
