Re: Can "optimization/pre-binding" be bypassed in 10.3.9 ?
Re: Can "optimization/pre-binding" be bypassed in 10.3.9 ?
- Subject: Re: Can "optimization/pre-binding" be bypassed in 10.3.9 ?
- From: Steven Lobo <email@hidden>
- Date: Tue, 24 Oct 2006 12:35:28 -0700
- Thread-topic: Can "optimization/pre-binding" be bypassed in 10.3.9 ?
Thanks for confirming.
Since I control the launching of packages from my application, I figured
that I can workaround this issue in 10.3.9 by launching the next package as
soon as the current package being run starts it's prebinding process. My UI
progress would thereafter track the progress of the newly launched package
while the previously run package would proceed with it's prebinding without
any UI support in my application. Launching a package when another one is
running might slow down the Mac slightly (not noticeably), but would still
maintain a shorter overall install time than with not doing so. I currently
monitor the "PHASE" and "STATUS" strings from the installer tool to update
my UI. I observed that I do get similar status strings even for the
prebinding process for a package and am wondering if this might be a
good/safe trigger to pursue the approach I mentioned above.
Could you pls. confirm if this is a safe method to rely on ? I would not
like to go down this path if there are known issues/shortcomings with this
approach.
Steven
On 10/24/06 11:21 AM, "Peter Bierman" <email@hidden> wrote:
> Your analysis is correct. The additional time needed in 10.3.x is due
> to update_prebinding. Unfortunately, there is no way to skip or
> coalesce this step in 10.3.x. Improving this was one of the major
> features of the 10.4 installer.
>
> -pmb
>
>
> At 9:42 AM -0700 10/24/06, Steven Lobo wrote:
>> Hi:
>>
>> I have a software updater application that downloads Packagemaker packages
>> from a server and launches these one after the other using the commandline
>> "installer" tool. I asynchronously monitor the status of the package
>> installation in my application and update a progress bar in the UI to
>> indicate install status. This application has to work in 10.3.9 and 10.4.8.
>>
>> Issue:
>> ======
>> I am observing that the install time in 10.3.9 for my updater application is
>> significantly longer than than the time it takes for the same operation to
>> occur with the same packages in 10.4.x. On further investigation, I
>> discovered that the additional time is being taken by the optimization
>> process (I guess pre-binding). It appears that this process is occurring for
>> each package run by the "installer" tool. This does not occur in 10.4.x and
>> later. In scenarios where there are a bunch of packages to run, the
>> additional time taken for this process is noticeably significant. Sometimes,
>> the optimization process takes more time to execute than the install process
>> itself! This time is unacceptable in 10.3.9 when the user has to download
>> and install the whole software suite (I also support reinstall from the
>> updater) that consists of at least 15-20 packages.
>>
>> Is this a known issue/observation ? What I would like to do is bypass having
>> each package installation execute this optimization process. I can perform
>> this separately from my code after all packages are installed. Are there any
>> realistic ways to resolve/workaround this issue ?
>>
>> Steven
-----------------------------------------------
Robosoft Technologies - Come home to Technology
_______________________________________________
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