Best Way to Deploy Xcode

Hi,

I just used composer, took a snap shot, installed and built, then
delpoyed via self service, its over 2GB so takes a while to deploy but
it worked fine

Criss

Criss Myers
Senior IT Analyst (Mac Services)
iPhone / iPad Developer
Apple Certified Technical Coordinator v10.5
LIS Development
Software Management Team
Adelphi Building AB28
University of Central Lancashire
Preston PR1 2HE
Ex 5050
01772 895050

Criss,

Thanks for the quick response. We originally did it that way too. But I
started to notice that even though some features worked in xcode, there were
random errors that occurred. I figured it might be due to missing files.

Dave

Hey Dave, this is what we do and it has been successful for us:

1. Create a folder in the the /private/tmp folder that will house the Xcode installer (in my example, the folder is called "xcode_install")
2. Copy the "Xcode and iOS SDK.mpkg" file to that folder
3. Also copy the invisible folder "Packages" that is in the Xcode Install disk image to that folder
4. Then drag the xcode_install folder into Composer
5. Build it as a .pkg with the postflight script below. The postflight script will install the .mpkg file and then remove the xcode_install folder.

Postflight script:

#!/bin/sh
## postflight

installer -pkg "/private/tmp/xcode_install/xcode/Xcode and iOS SDK.mpkg" -target /

rm -R /private/tmp/xcode_install

Travis

Thanks Travis,

I'll give that a shot.

Dave

Hey all,

Just a note on Travis' process. It all looks good, but before you create your package, be sure to adjust the Exclusion List in Composer's preferences, otherwise your files in /private/tmp will be ignored.

This was a head-banging-on-table experience for me a couple of years ago. Hopefully my experience can save someone a few lumps.

I hope this is helpful.

--

Miles Leacy

Technical Training Manager

Mobile +1 347 277 7321

miles at jamfsoftware.com<mailto:miles at jamfsoftware.com>

....................................................................

JAMF Software

1011 Washington Ave. S

Suite 350

Minneapolis, MN 55415

....................................................................

Office: (612) 605-6625

Facsimile: (612) 332-9054

....................................................................

US Support: (612) 216-1296

UK Support +44.(0)20.3002.3907

AU Support +61.(0)2.8014.7469

....................................................................

http://www.jamfsoftware.com<http://www.jamfsoftware.com/>

In modifying the Exlusion list; is this a step that should only be done the one time that this PKG is being created?
I guess I'm wondering if there would be major fall out from permanently removing this entry..

Nick Caro Senior Desktop Support Administrator

I'd expect you will see a lot of extra files in /private/tmp in any future packages built (using snapshots or fsevents monitoring) with that exclusion removed. Cleaning them up manually is likely to be a pain; that's why the exclusion list exists.

This is my take too. The list shouldn't affect building a package
On 2/17/11 10:39 AM, "Urban, Benjamin Mark" <BUrban at imf.org> wrote:
manually, which I do most of the time.

One thing I noticed in some testing (haven't reported this yet because I'm
still testing) is that deploying anything to /private/tmp using a .dmg
file seems to fail. If I want to deploy to /private/tmp I have to create a
.pkg file. I'm using Casper 7.31 still.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492