Seeking tips on packaging with PackageBuilder to get close to my apps existing Vise-base install experience?
Seeking tips on packaging with PackageBuilder to get close to my apps existing Vise-base install experience?
- Subject: Seeking tips on packaging with PackageBuilder to get close to my apps existing Vise-base install experience?
- From: "Chris Markle" <email@hidden>
- Date: Wed, 10 Dec 2008 22:14:54 -0800
Pretty new to PackageBuilder here... Sending this out in hopes of
getting some tips that might save me some time and keep me from
running into brick walls.
We've inherited this app that's today packaged using some release of
Vise. The installation package has some nice properties where if an
admin user installs it, it can easily go into /Applications but if a
standard user installs it, it goes smoothly into ~/Applications. It
does this without prompting for admin passwords unless really
necessary. And it manages to do this on 10.3, 10.4 and 10.5 (not sure
I care about 10.3 moving forward but I do care about 10.5).
Looking for idea of how I can simulate this behavior as closely as
possible with an installation package built with PackageBuilder. I
have the 3.0.3 verison of PackageBuilder on OS X 10.5.5. I've been
playing with making the install destination System Volume or User Home
Directory and using the /Applications target. On 10.5 this basically
gives the user a choice of "install for all user" or "install for one
user" and this seems to work reasonably well. I am not checking
"require admin authorization" as it seems that that always prompts for
the admin password, no matter what (not sure of that however). On 10.4
the resulting installer can't go into the User Home Dir and only goes
into system volume. But the 10.4 install being installed by a
non-admin user would require me to have that admin password prompting
enabled. Is there a reasonable way to make an install package the
works more closely to the Vise case, for both 10.4 and 10.5.
Another question: In the 10.5 case where we can "install for all" or
"install for one" it seems that the default is always install for one.
Can the default be more dynamic based on the perms of the user so
e.g., if they have admin privs, the default would be "install for all"
but if they have "standard" privs the default would be "install for
one"?
Any help on these questions us really appreciated and thanks in advance...
Chris
_______________________________________________
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