You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+40-2Lines changed: 40 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,32 @@
1
-
# quickpkg
1
+
# `quickpkg`
2
+
3
+
This tool will quickly and easily build a package from an installed application, a disk image file or zip archive with an enclosed application bundle. It will also extract the application name and version and use it to name the resulting `pkg` file.
4
+
5
+
The tool will look for applications on the first level of the disk image or archive. If it finds no or more than one application it will error.
6
+
7
+
The name of the resulting package will be of the form `{name}-{version}.pkg`. Spaces will be removed from the name. The package will be written to the current working directory.
8
+
9
+
## Examples
10
+
11
+
Build package from installed application:
12
+
13
+
```
14
+
quickpkg /Applications/Numbers.app
15
+
```
16
+
17
+
Build package from a disk image:
18
+
19
+
```
20
+
quickpkg ~/Downloads/Firefox\ 43.0.4.dmg
21
+
```
22
+
23
+
Build package from a zip archive:
24
+
25
+
```
26
+
quickpkg ~/Downloads/Things.zip
27
+
```
28
+
29
+
## Background
2
30
3
31
OS X has had the `pkgbuild` tool since Xcode 3.2 on Snow Leopard. With pkgbuild you can directly build a installer package from an application in the `/Applications` folder:
This tool even does the work of determining a bundle's identifier and version and sets the identifier and version of the pkg to the same values.
18
46
19
-
However, `pkgbuild` does not
47
+
However, `pkgbuild` does not automatically name the package.
48
+
49
+
## `quickpkg` vs `autopkg`
50
+
51
+
This tool is not meant to replace [`autopkg`](https://github.com/autopkg/autopkg). `autopkg` will automate the download, the re-packaging (if necessary) and the upload to and configuration of your client management system. It can also handle much more complex setups than `quickpkg`. `autopkg` is far superior and should be your tool of choice.
52
+
53
+
However, there are situations where `autopkg` does not work well. The most common reason is if the download cannot be automated because the download page is behind a paywall. Also `autopkg` requires a recipe for a given piece of software. If no recipe exists, `quickpkg` may be a simple alternative. (Though if `quickpkg` works, creating an `autopkg` recipe should not be hard.)
54
+
55
+
## Warning
56
+
57
+
All `quickpkg` does is identify an application bundle and package it in a way that the package will install that application bundle into the `/Applications` folder. If the application needs other files (libraries, frameworks, configuration files, license files, preferences etc.) to run and work they are your responsibility.
0 commit comments