updated Readme for 0.3

Author: scriptingosx

README.md

@@ -32,6 +32,42 @@ quickpkg ~/Downloads/Things.zip
 
 Pass a folder with scripts that are passed to `pkgbuild`'s `--scripts` option. If the there is a `preinstall` and/or `postinstall` script they will be run at the respective and can call other scripts in this folder.
 
+### `--postinstall postinstall_script`
+
+Use the script file given as a postinstall script. If given together with the `-scripts` option will attempt to merge the two and error if a `postinstall` script is already present.
+
+### `--preinstall preinstall_script`
+
+Use the script file given as a preinstall script. If given together with the `-scripts` option will attempt to merge the two and error if a `preinstall` script is already present.
+
+### `--ownership {recommended,preserve,preserve-other}`
+
+This parameter will be passed into `pkgbuild`. Default is `recommended`. See `man pkgbuild` for details.
+
+### `--output pkgpath`
+
+Will write the resulting package to `pkgpath` instead of the current working directory. If `pkgpath` is a directory, then the default package name (`{name}-{version}.pkg`) is used. You can also give the complete path, including a name. You can use the placeholders `{name}`, `{version}` and `{identifier}` in the name.
+
+Examples:
+
+```
+quickpkg /Applications/Numbers.app --output ~/Packages/
+```
+
+Will create `Numbers-X.Y.Z.pkg` in `~/Packages`.
+
+```
+quickpkg /Applications/Numbers.app --output Numbers_latest.pkg
+```
+
+will create `Numbers_latest.pkg` in the current working directory.
+
+```
+quickpkg /Applications/Numbers.app --output ~/Packages/{identifier}_{version}.pkg
+```
+
+will create `com.apple.Numbers_X.Y.Z.pkg` in `~/Packages`.
+
 ## Background
 
 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:
@@ -56,11 +92,11 @@ However, while `pkgbuild` does automatically name the package, it does not inclu
 
 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.
 
-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.) 
+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. Or maybe you are just experimenting with a test server and do not want to change your production `autopkg` setup. 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.) 
 
-## `quickpkg` vs `munki-pkg`
+## `quickpkg` vs `munkipkg`
 
-`quickpkg` is meant for 'quick' packaging. No configuration, no options. Download the application from the AppStore or the dmg or zip from the web and go. (I started working on it because I could never remember the exact options needed for `pkgbuild`.) [`munki-pkg`](https://github.com/munki/munki-pkg/) is a tool that makes it easier to access the complex options of `pkgbuild` and `packagebuild`, but it still supports complex projects. 
+`quickpkg` is meant for 'quick' packaging. No configuration, no options. Download the application from the AppStore or the dmg or zip from the web and go. (I started working on it because I could never remember the exact options needed for `pkgbuild`.) [`munkipkg`](https://github.com/munki/munki-pkg/) is a tool that makes it easier to access the complex options of `pkgbuild` and `packagebuild`, but it still supports complex projects. 
 
 If you prefer a UI rather than a command line tool, then use [Stéphane Sudre's Packages](http://s.sudre.free.fr/Software/Packages/about.html).