Skip to main content
Question

Problem with complex installations in Lion

  • December 6, 2011
  • 4 replies
  • 19 views
P
Forum|alt.badge.img+6

Hey Casper Braintrust,

Have been having some odd problems with some complex installations to 10.7.x systems. Specifically with my Xcode installer and Checkpoint FDE. I created these to create a temp folder in the /tmp location and place the required packages to be installed within it. Then I called the installers with a post flight script. These have worked great in Snow Leopard, but no longer in Lion. I am sure is has to do with changes to the new OS. Is anyone out there doing similar installations for your more complex installs and found a solution to doing these installations.

Thanks

Paul Austin

End User Computing, Platform Engineering

Wells Fargo | 1525 West W.T. Harris Blvd | Charlotte, NC 28262
MAC D1112-036
Tel 704 427-0903

    4 replies

    bentoms
    Forum|alt.badge.img+35
    • bentoms
    • Hall of Fame
    • December 6, 2011

    Are you seeing any error messages?

    Do they install normally ok?

    Regards,

    Ben.

    P
    Forum|alt.badge.img+6
    • paulaust
    • Author
    • Contributor
    • December 6, 2011

    Both of the installations fail. According to the install.log they usually
    fail inside a sub package script. The one that is driving the most crazy
    at the moment is CheckPoint FDE. The installer for FDE has an "isp" file
    that has to coexist in the same directory as the installer to do a silent
    install with the correct settings. The installer native installer from the
    vendor is a mpkg. I placed the mpkg and the isp filed into
    /tmp/fde_install and captured them with Composer, then created a post
    flight script to install the fde mpkg package. This works great in 10.5
    and 10.6. 10.7 blows up running a script in one of the sub packages inside
    the main installer that references the isp file that is in the same tmp
    directory. I am wondering if Lion is running the installer in a "sandbox"
    type mode so it can't fully read the isp file. Funny thing, is this only
    fails if I run the package through casper. Policy, Self Service or Remote
    all fail. If I run the installer from the desktop, it runs like a champ.

    Paul Austin

    End User Computing, Platform Engineering

    Wells Fargo | 1525 West W.T. Harris Blvd | Charlotte, NC 28262
    MAC D1112-036
    Tel 704 427-0903

    paul.austin at wellsfargo.com

    A
    • Anonymous
    • December 12, 2011

    Try putting the stuff you would have dumped in /private/tmp inside the
    On 7 December 2011 05:10, <Paul.Austin at wellsfargo.com> wrote:
    package's Resources, then do what needs to be done in the post scripts
    using the $1 variable. For example:

    postflight:
    #!/bin/sh

    installer -target / -verbose -pkg $1/Contents/Resources/XCode.mpkg

    donmontalvo
    Forum|alt.badge.img+36
    • donmontalvo
    • Hall of Fame
    • December 13, 2011

    A good example of this kind of workflow is the Parallels deployment wrapper. When deploying virtual machines, the wrapper's postflight script will mv them into /Users/Shared/Parallels directory.
    Doug Brown wrote:

    For most deployments we've been installing into the /tmp directory but it's definitely time to review the workflow and adapt the above.

    Don

    --https://donmontalvo.com
    Terms & ConditionsCookie settingsAccessibility statement