Is Packages still a decent solution for creating a package installer? [...] My app is not just a simple install into the Applications folder; there are a number of other files that need to go into various system level directories. As it's a much older Carbon-based app, it is still compiled on Xcode 3.6.2 (in Mavericks) and hence I cannot use any of the newer Xcode-based packaging tools. If not Packages, what would you suggest? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com What newer Xcode-based packaging tools are you referring to? I am not aware of any. If you are referring to the command line tools, they are quite independent of Xcode. Many people here are perfectly happy with Packages, so you may want to give it a try. Personally, I haven't used it so I can't comment further on it. What I have done is made my own packaging scripts that I run as an Xcode build phase. While I can now fortunately run these in a modern Xcode, for a while there I was using the older command-line packaging tools in Xcode 3.2.6 running in a Snow Leopard Server virtual machine. The plus side for me is that I don't have to launch an external tool. I can just do the entire build and packaging creation within Xcode. Also, I find that this approach is more SCM friendly than the old PackageMaker approach, though I have been told on this list that Packages' file format is also SCM friendly. Since you are running Xcode 3.2.6 on Mavericks, and since I am recommending simple "Run script" build phases, those scripts are perfectly capable of running the Mavericks versions of the packaging commands. So you can build yourself a nice modern flat package that will still target back to at least Snow Leopard.