Re: Forcing order of packages in a metapackage
Re: Forcing order of packages in a metapackage
- Subject: Re: Forcing order of packages in a metapackage
- From: "Bryan S. Lee" <email@hidden>
- Date: Thu, 29 May 2008 22:33:04 -0400
- Thread-topic: Forcing order of packages in a metapackage
Title: Re: Forcing order of packages in a metapackage
I’m not sure about Iceberg, but with PackageMaker 3.01 (with one major exception) it seems to follow the order that choice/contents are put into the main package (which boggles me that I am unable to re-order the items from within the GUI).
The exception being that if I have a content item that is stored internal to the main distribution package and have other content packages that are pulled from a URL, it will install (and run scripts) on the internal items first, irregardless of the order that they are placed into the package.
This bit me while building an installer to redistribute several applications. I had 3 separate pieces that dealt with Microsoft Office 2008, first would download and install Office, second would download and install the Office SP1 update, third was nothing more than a cleanup script stored internally and installed into a /tmp directory then set to run itself as a postscript which would remove the previously downloaded installers and some /tmp clutter. Since the 3rd part was stored internally, it would cleanup before the other parts deployed.
--
Bryan S. Lee
Information Resource Consultant II
Computer Support Services
Clemson Computing and Information Technology
Clemson University
email@hidden
ACHDS 10.4, MCP NTS/NTW
From: Taylor Armstrong <email@hidden>
Date: Thu, 29 May 2008 11:31:35 -0400
To: <email@hidden>
Subject: Forcing order of packages in a metapackage
Testing something the other day and realized some odd behavior.
Building a package for Acrobat 8 Pro. I have the Acrobat 8 install .pkg
built, and it seems to work well. My next task was to un-install
previous versions of Acrobat reader and Acrobat pro.
Using InstallEase, I created an un-install .pkg for each version I need
to remove. Tested each, all appears well.
I then built a metapackage using Iceberg, with the packages in the
following order:
Remove Acrobat 6 Pro
Remove Acrobat 7 Reader
Remove Acrobat 7 Pro
Remove Acrobat 8 Reader
Install Acrobat 8 Pro.
I'm pushing the package out via ARD, but noticed somthing when testing
it... the packages are not always deployed in that order. In at least
a couple of cases, I've seen it run one or two "remove" packages,
install Acrobat 8 Pro, and then remove a couple of others. I'm just
worried about a "remove" package accidentally deleting some resource
that may be used by 8 Pro.
For now, I'm avoiding the situation by separating out the "remove"
pacakges, running them first, and then only running the Install package
by itself after confirming the earlier package, but is there a good,
reliable way to set the order and create dependencies that the prior
package completed successfully? I'm a relative newbie to packaging, but
am definitely trying to make sure I learn the "right way" before I get
into too many bad habits.
thanks,
Taylor
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
W. Taylor Armstrong email@hidden
National Ocean Service IT Support
1305 East-West Highway
Silver Spring, MD 20910
Phone (301) 713-2644
http://nos.noaa.gov/
IT Support Request Email: email@hidden
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden