Steps for building an OSX .pkg file for releases

[GoogleCodeExporter]

Hello!

I noticed that download for Pencil's OSX release is a .tar.bz2 file. If you 
have interest, the following will convert that .tar.bz2 to an OSX .pkg file for 
(hopefully) easier installation:

fpm -s tar -t osxpkg -n Pencil -v 2.0.6 --prefix /Applications/ 
Pencil-2.0.6-mac.tar.bz2

This requires fpm (an open source tool I help maintain) and ruby to achieve.

Once the .pkg file is made, users can install it by double-clicking, and the 
resulting package will install to /Applications/ (and request elevated 
credentials to write to that location during the install).

If you find this useful, sweet! If not, that's ok :)

---

Example use:

# Creating the package (usually by the release process)
% fpm -s tar -t osxpkg -n Pencil -v 2.0.6 --prefix /Applications/ 
Pencil-2.0.6-mac.tar.bz2
Created package {:path=>"Pencil-2.0.6.pkg"}

# As a user
% open Pencil-2.0.6.pkg
... Normal OSX package installer UI presents itself ...
% ls -ld /Applications/Pencil.app
drwxr-xr-x  3 root  wheel  102 Apr 13 18:02 /Applications/Pencil.app/

Original issue reported on code.google.com by j...@semicomplete.com on 14 Apr 2015 at 1:07

[GoogleCodeExporter]

I see you already produce an RPM, cool! fpm can also be used to build rpms and 
debs, if that suits your needs. Happy to help with any questions if you want to 
use this to help build packages. :)

Original comment by j...@semicomplete.com on 14 Apr 2015 at 1:08