Leopard PackageMaker Issues

[dano]

I am unable to generate package installs under Leopard’s PackageMaker application. Small packages work but when I attemp to create larger packages for applications like Office 2008 or CS3, PackageMaker typically crashes after processing awhile. Using a Tiger install with PackageMaker, I can successfully generate Office or CS3 pakcages.

[dano]

My apologies….I should have been clearer. I was really looking to find out if anyone else here has experienced Leopard packageMaker issues. I was considering a bug report but thought I’d find out a little more information and probably some more testing before doing that.

[jdyck]

I also have experienced the problems with Leopard’s Packagemaker… It’s fine for smaller installers, but anything big, like Adobe CS3 or MS Office seems to pretty much lock it up. I’ve jumped to IceBerg for those cases,but since I’m going to have to be training more Jr staff to create these packages it would be nice to have just one workflow.

[pepijn]

After trying to make Leopard’s PM work and failing, I have switched back to using the previous version 2.1.1 which works fine with Leopard. It seems like the version bundled with Xcode 3.x needs some work still.

p.

[ewhite]

@pepijn: How did you get PackageMaker 2 installed on a Leopard Mac?

[ewhite]

@jdyck: Based on your comment above, I tried IceBerg (using logGen and PkgGen based on this workflow: http://blog.irisink.com/?p=106) and finally got my Adobe CS3 packages working, thanks for the tip!

[dano]

Well….I’ve finally revisited Leopard PackageMaker. As I initially reported I couldn’t get PackageMaker 3.x to build a custom package comprised of Adobe Creative Suite 3 (Design Premium) or Office 2008. I haven’t tried Office yet but have discovered what the issue is with CS3.

PackageMaker builds fail when PackageMaker encounters directory/file names that include the tilde (~) character. Removing the tilde character in names prior to attempting a package build results in a successful build. Photoshop and DreamWeaver both have directories/files that contain a tilde in the name. They are:

/Applications/Adobe Photoshop CS3/Plugins/Extensions/Bigger Tiles/~Bigger Tiles.plugin
/Applications/Adobe DreamWeaver CS3/configuration/Behaviours/Actions/~Deprecated
/Applications/Adobe DreamWeaver CS3/configuration/Snippets/~Deprecated

I’ve filed a bug report with Apple. In the meantime as a workaround I remove the tilde character from the names prior to building the package and then restore the tilde character to the names as a post install script. Note: Due to the size of CS3 I’ve only tested CS3 components located within the Applications directory so far. I am now moving on to the remaining Application Support and other miscellaneous CS3 components. Stay tuned.

[dano]

I have successfully created a full CS3 Design Premium package using Leopard’s PackageMaker. There are no additional problem files to the one mentioned in my previous post. My package is CS3 without updates applied.

[e_whizz]

I also removed the following before packaging…

/Applications/Adobe\ Illustrator\ CS3/Plug-ins.localized/Extensions.localized/UniversalTypeAICS3.aip
/Applications/Adobe\ InDesign\ CS3/Plug-Ins/UniversalTypeIDCS3.InDesignPlugin

These will be there if you have installed Extensis Universal type server.
These also cause packagemaker to choke, I have found….

Luckily Extensis package the installer up for this pretty well, I just use theirs.

[Author]

Posts