[dano]

Clarification: Using this method I have been able to do things like removing choices for paper sizes, in the Page setup dialog, that aren’t loaded into a printer (we don’t permit user supplied paper manual feed situations)

[dano]

A couple of other suggestions:

1. Depending on how sophisticated your printing hardware is you might be able to set this up from the printer end of things. You would need to be looking at workgroup class printing hardware with some reasonable print administration capabilities.

2. Modify printer PPD files. Printer options available through Mac OS X Print and Page Setup windows are established by a printer’s PPD file. By editing the file it is possible to change defaults or limit options available to the end user. This only works if you have control over the end user’s computer, such as in a computer lab. Using this method I have been able to do things like deleting paper sizes that weren’t available to the end user (we don’t permit user supplied paper manual feed situations)

[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.

[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]

All you should need to do is check the iLifeSupport.pkg. Now that I think about it, iLife updates wouldn’t be rolled into a combo updater so ignore what I said about the v4.11 Combo updater.

[dano]

Disclaimer: I’ve only been testing under Leopard but I did experience issues related to iLife just like what you’ve described.

The issue is such that the software upodate in question works fine if you are updating on your current boot volume but doesn’t work when installing to a non boot volume like your disk image. Check out a forum labeled “Apple updates and update order” and search for a post under my name. The update in question is iLifeSupport.mpkg and my post describes the fix. If the update is part of a combo updater you will probably have to view the contents of the combo updater in order to hunt down the problem package.

Hope this helps

[dano]

In the overall scheme of things the increased intall time for Apple Updates (including the 10.5.2 and 10.5.2.3 Combo Updaters together) required is minor. I’ve gone from about 20 minutes to about 25 minutes to install Apple updates. Additional time to the overall build is probably on the order of 6-10 minutes for a build that is approaching 3 hours (CS3 Design Premium and Office 2008 included) to complete. Not to mention that I can start a script and come back when it’s done for a ready to use disk image.

Having said that, I think there is value in changing the updates that are placed in the AppleUpdates folder as available updates are added and others are superseded. It really isn’t necessary but doing so would simplify the Apple Updates portion of the process and that’s never a bad thing. FYI: I will being doing just that in late July (I work at an educational institution) when I am ready to roll out Production ready images. But as I’m still fine tuning my build process I’m just adding any new Apple updates to my previous ones as they appear and it’s been working just fine for me that way.

[dano]

I added the newer Software Updates to the build train without removing any older updates as the previous poster did and had no difficulties. It shouldn’t be necessary to remove the the Mac OS X combo updater or other older updates (barring any problems with specific updates). After all, this replicates the typical update path of the average user.

[dano]

…..as to whether creating custom packages is the best solution? For me it is. The packages I’ve been testing install much more quickly then installing using Adobe’s install mechanism. The Adobe base CS3 installer is very inefficient. Adobe’s CS3 installer copies each file individually, then checks the proper GID and UID for the path to the file, and sets it. One at a time. My custom CS3 installer takes close to 5 minutes to install on a MBP laptop. Adobe’s takes about 21 minutes (from a disk image of the install DVD). Installing all the custom packages of my InstaDMG build train takes 19 minutes total. Of which, I estimate, CS3 and CS3 updates take about 13 minutes. Compared to approximately 1.5 hours for CS3 + updates using Adobe’s installer and updater mechanism.

I am employed at an educational institution and am primarily interested in building images for Mac computer labs. But I do perform the occasional “one off” CS3 install for staff members. Being able to perform a CS3 install plus updates in under 15 minutes is a great boon. Your needs will no doubt vary.

If you do go the custom installer package route, I would suggest the following:

1. Create a package for the CS3 bundle excluding updates. I should add that we install the full CS3 Design Premium bundle in all labs so I don’t have to worry about installing portions of CS3 bundles here. Having said that it shouldn’t be difficult to break the bundle down into its component applications.

2. Launch Adobe Updater and make note of the updates listed. Install each update one at a time and generate a package for each update. Use Adobe Updater to verify that you have installed all Adobe updates. Optional: Bundle up all the Adobe updates in a metapackage. This is what I do.

Final comment: Keeping everything in individual packages makes for a modular and very flexible build process. It’s relativeley easy to add new Adobe updates that come down the pike. One last note. Adobe has discontinued Adobe Stock Photos. Adobe provides a special uninstaller which uninstalls the Bridge plugin but it doesn’t delete the Stock Photos folder. If you create a package to delete Stock Photos (and the Stock Photos directory) make sure you install it after all the Adobe updates have been installed. Some of the updates will recreate the Stock Photos directory.

[dano]

There is an issue with Leopard’s version of Developer Tools which has been noted on other afp548 threads. I’ve been able to generate smaller packages but not Office 2008 or Adobe CS3 Design Premium pakcages. Others have reported having this issue as well. This problem affects PackageMaker and InstallEase as both use use Developer Tools to build the packages. Whereas Tiger’s Developer Tools has no difficulty generating Office or CS3 packages. Check out the “Leopard PackageMaker Issues” thread for more information

[dano]

1. Read the thread entitled “Apple updates and update order”. Search for a post under my name. This details the specific order for Apple Updates. There are a couple of updates that are problematic but can be fixed. Details for the necessary fixes are included in the post. If you have downloaded your Apple updates via the Software Updates control panel verify that the downloads are proper package installers. I had a couple that I had downloaded that were not in the proper package “wrapper”. They were in a regular folder. I ended up downloading the problem packages from the Apple Downloads section of their website.

2. If everything checks out per the previous step. I would then test the process by disabling some steps in the InstaDMG script process by commenting out certain sections of the script to test the process. Or, if you are not scripting savvy, remove the Apple Updates and Custom Packages from the appropriate folders. First I would try building a base image without Apple Updates and Custom Packages. If that works, then add Apple Updates and try it again. If everything works again, then add the Custom Packages and see if it works. You should be able to isolate where the process is failing using this methodology.

Hope this helps!

[dano]

A couple of things regarding the logGen to pkgGen to PackageMaker workflow:

1. logGen doesn’t scan user’s home directory. This isn’t a major issue unless you would like to see what user settings are generated or modified.
2. pkgGen has problems with symlinks and will generate an error upon encountering a symlink.
3. Leopard’s Developer Tools appear to be rather buggy. I haven’t been able to generate packages for Office 2008 or Adobe CS3 using Leopard’s Developer Tools while Tiger’s Developer Tools work just fine.

FYI: I’m not familiar with Composer but am growing fond of an application called LANrev InstallEase. If you’re not as comfortable using the command line then this is a good GUI based method of generating pakcages. You still need Developer Tools installed to build your package installers. The company that publishes LANrev was (may still be) offering InstallEase as a free download. It has been offered as commercial software in the past.

[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.

[dano]

…if you are manually defining your UID make sure you are not using the same UID for both accounts you are trying to create

[dano]

I’m assuming you are editing the file named “USERDATA” (/Volumes/createUser/createUser.pkg/Contents/Resources/USERDATA). And only editing the “shortname” and “longname” properties.

For the “Unique ID” (UID) you have two options. Insert a value to define the user’s UID or don’t define anything and let the script figure out an available UID starting at #501

[Author]

Posts