Home Forums Software InstaDMG Is there a method to use flat packages like xcode in instaDMG?

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #378298
    jeffbearer
    Participant

    I’m trying to roll xcode into my image. I see that the xcode.mpkg is a flat package and it calls a bushel of other packages that are in a hidden folder on the xcode dmg.

    I’ve tried just including the code dmg by hand like this as InstaUp2Date chokes on xcode:

    [code]
    # pwd
    /…../instadmg/InstallerFiles/BaseUpdates
    # ls
    9 -> ../InstaUp2DatePackages/xcode321_10m2003_developerdvd.dmg
    [/code]

    It runs the xcode.mpkg but does not seem to do anything as it only takes 9 seconds to run:

    [code]
    Working on folder 9 (07:52:06)
    Mounting the package dmg: xcode321_10m2003_developerdvd.dmg (./InstallerFiles/BaseUpdates/9) at: /private/tmp/InstaDMG_temp_folder.VisiwP/mount_point.ffXux2
    Installing Xcode.mpkg from ../InstaUp2DatePackages/xcode321_10m2003_developerdvd.dmg (9)
    Folder 9 done (07:52:15)
    [/code]

    I also see in the instadmg.bash this comment

    [code]
    # check to see if this package should be excluded from the chroot system
    if [ -d “$UPDATE_PKG” ]; then
    # does not work on flat packages

    PACKAGE_BUNDLE_ID=`/usr/bin/defaults read “$UPDATE_PKG/Contents/Info” “CFBundleIdentifier” 2>/dev/null`
    PACKAGE_CHROOT_DISABLE=`/usr/bin/defaults read “$UPDATE_PKG/Contents/Info” “InstaDMG Chroot Disable” 2>/dev/null`
    [/code]

    Not sure if that means that chroot does not work on flat packages, or instadmg does not work on flat packages in general.

    So does anybody have a method I can use to install xcode.mpkg and help me with the tedium of installing all the hidden packages or is my only option to set up a few dozen symlinks in the BaseUpdates folder for every package in xcode?

    #378299
    jeffbearer
    Participant

    Please forgive me, this is indeed a duplicate of the other recent code post. I didn’t grok what he was seeing till just now.

    Here is the meat from my debug log:

    [code]PHASE:Preparing Xcode…
    IFPKInstallElement (18 packages)
    An exception was thrown from the install queue while running IFPKInstallElement. IFPKInstallElementException. Package PKLeopardPackage cannot be installed at /tmp/InstaDMG_temp_folder.VisiwP/mount_point.B2QZKy/Developer using destination path /private/tmp/InstaDMG_temp_folder.VisiwP/mount_point.B2QZKy/Developer.
    Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
    The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

    Unmounted the Package DMG image from /private/tmp/InstaDMG_temp_folder.VisiwP/mount_point.ffXux2
    [/code]

    #378300
    Allister Banks
    Participant

    You’ll pardon me as it may be obvious to others but, is this while booted from a 10.5.x system, making a 10.5.x build? I can’t imagine flat packages don’t work, I’m sure there are apple updates that are flat.

    If anyone can explain line 930(block begins on 856, install_packages_from_folder) of the script better please enlighten me, but I believe that comment is saying that flat packages can’t be excluded using the -d flag. Then again I can’t tell what is being passed the -d flag either….

    I do remember this being a hangup that there have been less-than-elegant workarounds for, one being a script than ran as soon as the booted image hit loginwindow the first time – which locked out the users until it was complete. Not sure if this could be accomplished by a deploystudio install package post-imaging step if it really is not possible to work around.

    Allister

    #378301
    jeffbearer
    Participant

    10.6.2 on the build machine and the image.

    #378302
    Allister Banks
    Participant

    I don’t have a leopard setup available be able to tell if xcode will work in 10.5.x, but with the lack of chroot jails altogether in 10.6(and, if we were to speculate, for the foreseeable future while bugs remain unresolved,) there is little reason to believe it can be worked around.

    Please ensure you are using at least 1.6b2, which chroots the installer daemon itself(while still not being able to wrap the entire temporary image as we were able to in Leopard.) The most recent revision of the instadmg.bash script from svn would be 266, which you would see on line 12.
    I’ll test this on my system the next chance I get.

    Allister

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.

Comments are closed