Re: some notes on package maker - external files
Re: some notes on package maker - external files
- Subject: Re: some notes on package maker - external files
- From: Stéphane Sudre <email@hidden>
- Date: Fri, 8 Jul 2005 08:24:54 +0200
On vendredi, juillet 8, 2005, at 05:32 AM, Peter Bierman wrote:
At 3:16 PM +1200 7/8/05, rodney tamblyn wrote:
Andy,
Thanks for the reply - Stephane's site sure is great.
There's an alternative to moving your items via shell script like I
have
done... In your preflight, make a symbolic link named
\tmp\aVeryVeryUniqueName to {$HOME}/whatever/. In PackageMaker, of
course
then set \tmp\aVeryVeryUniqueNam to be your target dir, and you'll
be all
set! With this method, the install process will correctly report the
install footprint size when the user is interacting with the
installer and
the progress bar will be accurate (something which may be crucial in
your
case since you mentioned that you have very large data files to
install).
Don't forget to get rid of your temp symbolic link after you're done!
I'm confused how the installer will know size of the files if they
are being stored externally? Surely this will get us back to the
situation where the 400Mb of files have to be included in the
installer payload?
This may not be helpful for you, but if you're using a distribution
script, you can explicitly declare the size of the package for the
purposes of the UI. That probably won't get the progress bar to look
right though.
Without a distribution script, would it be possible to do this by
changing the .sizes files?
BTW, isn't there a IFPkgPayload flag? I thought I saw one in a package.
_______________________________________________
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