Sorry for a long delay. As I posted in the pull request #231, we are ready to make progress on this. I've attempted a merge, and I've pushed the result into a branch.
Would you or Ingo verify my assumption that we still need to overwrite the scripts by those in the master? Are there anything else that needs to be done before merging this into the master?
On 02/18/2012 01:35 PM, Sami Tikka wrote:
What is the OS X version of the host where Mac installer is built? And should we start thinking about signing the installer? I'm asking because there's a pull request (https://github.com/jenkinsci/jenkins/pull/231) that would be useful to merge. The PR changes the tools used to create the installer to the latest Apple packaging tools (productbuild and packagebuild). These tools are only available in Xcode 4, which requires 10.6. This week Apple announced their next OS version and at the same time made available updated version of Xcode and related tools. The new tools no longer contain a command-line version of the PackageMaker, the tool currently used to create the Jenkins Mac installer. It would be important to merge PR#231 if we want to upgrade to latest Apple tool chain. We might soon be forced to upgrade: OS X 10.8 is going to only allow installing software signed with a certificate from Apple and this might require using the latest tools. (Yes, it will be possible to configure 10.8 to allow unsigned software, but that is not the default.) The PR#231 is several months old and needs rework in order to merge cleanly and take into account the latest Mac installer improvements, like setting up launchd job as a user with a writable home directory. Is anyone going to do it? I can do it if no-one else is interested. After PR#231 is merged, we should upgrade the Mac installer build machine to 10.7.3 and install the latest tool chain. Where is the Mac installer build machine? Who takes care of it? -- Sami .
-- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
