![]() The package project directory may also contain a "scripts" directory containing any scripts (and, optionally, additional files used by the scripts) to be included in the package. More typically, the directory also contains a "ist" file containing specific settings for the build. At its simplest, a package project directory is a directory containing a "payload" directory, which itself contains the files to be packaged. Munkipkg builds packages from a "package project directory". Munkipkg builds flat packages using Apple's pkgbuild and productbuild tools. ![]() Finally, munkipkg can import existing packages. It can easily build distribution-style packages and can sign them. ![]() ![]() It does not install a root-level system daemon as does autopkg. It can use JSON for its build settings file/data, instead of Makefile systax or XML plists. So why consider using munkipkg? It's simple and self-contained, with no external dependencies. It's definitely possible to use autopkg to build packages from files and scripts on your local disk. ![]() If you are happily using The Luggage, you can probably safely ignore this tool.Īutopkg ( ) is another tool that has some overlap here. While you can use munkipkg to generate packages for use with Munki ( ), the packages munkipkg builds are just normal Apple installer packages usable anywhere you can use Apple installer packages.įiles, scripts, and metadata are stored in a way that is easy to track and manage using a version control system like git.Īnother tool that solves a similar problem is Joe Block's The Luggage ( ). Munkipkg is a simple tool for building packages in a consistent, repeatable manner from source files and scripts in a project directory. Munkipkg A simple packaging tool for OS X. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |