Re: PackageMaker 3.0.1 problems
Re: PackageMaker 3.0.1 problems
- Subject: Re: PackageMaker 3.0.1 problems
- From: Paul FitzGerald <email@hidden>
- Date: Wed, 20 Feb 2008 15:03:21 -0800
On Feb 20, 2008, at 2:46 PM, Stéphane Sudre wrote:
On Feb 19, 2008, at 9:59 PM, Paul FitzGerald wrote:
On Feb 15, 2008, at 2:56 PM, Paul FitzGerald wrote:
On Feb 15, 2008, at 2:29 PM, Stéphane Sudre wrote:
On Feb 15, 2008, at 12:29 AM, Paul FitzGerald wrote:
So, I started with a new startup company and I'm the only Mac Engineer. That means I now have to build my own installers. Log time Mac developer, new to PackageMaker.
What I want to do is to use the PackageMaker GUI to setup a pmdoc file that I can call from a shell script to package up our product.
I'm having several issues. The biggest one is consistency. It seems that every installer I build (currently building from the GUI) behaves differently. So far I can't nail down specifics. But I'd like to get a feel for the stability of this version of PackageMaker before I go nuts.
Two issues that I'm having problems with are...
1) Setting Owner/Group/Mode. I want to set Owner to root and Group to Admin and one directory in the app need write access for everyone. The permissions in the app are already set as I need them but the Owner/Group is not. It seems that sometimes the installer does what I want and sometimes it does not.
2) I have a Postinstall Action that is suppose to launch the application when the installer is done. (I'd also like the installer to quit post install as well) I've seen it work a couple of times but usually nothing happens.
I am using the PackageMakers Users Guide as my reference.
Thanks for any help and pointer in the right direction,
Which package format do you use (or to be PackageMaker compliant, which OS do you target when you create your project)?
A postinstall action does not mean the same thing depending on the package format...
--
Stephane
I had to stop and think about what you were asking. Since I was using the GUI "target" wasn't clicking. I'm targeting 10.4 for the app. I also have given up on the GUI and am trying to put it together from the command line. Slowly building it up while re-reading "Software Delivery Guide"
I'm making progress ever so slowly.
I am now building a component package from the command line using the following (formatted for readability)...
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
-t Name
-b
-m
--target 10.4
-h system
-r build/Release/temp
-f resources/install_resources/Info.plist
-e resources/install_resources/Resources
-s resources/install_resources/Scripts
-o "Name.pkg"
This is working out OK but I want to embed this into a Distribution Package.
I've hand-rolled one that works for me but there are some things in the distribution.dist file that may not be exactly correct (like installKBytes="5000"). I started by editing a distribution.dist file from a previous failed attempt at using the GUI.
So, my question...
Is there a way to build a distribution package from the command line that incorporates an existing flat package?
If you're targeting Mac OS X 10.4, you can't use a flat package. Flat packages are 10.5 or later.
AFAIK, there are 2 ways to do a distribution script:
- you create a metapackage and then you add your distribution script inside the metapackage.
- you create a package and then you create your distribution script (For instance this is what the FrontRowUpdate2.1.2 update looks like).
I'm not sure you can create just a distribution script using the command line tool. I don't have a good experience with the command line tool as, at this time, I mainly use the GUI or a text editor when I need to work on the dist script itself.
Regarding the installKBytes info, this attribute is optional. So you can omit it.
To answer your question regarding point (2), you can use su $USER -c 'open thepathtoyourapplication'
Thanks I was able to get PackageMaker to do what I wanted with a --doc attribute. OMG PackageMaker did something useful! I think I'm set now. Thanks for the help.
Paul
|
_______________________________________________
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