PackageMaker for Leopard...how NOT to create an...
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Yo..
Since installing the Leopard developer tools, every package create using PackageMaker, when built, is built as a Metapackage (mpkg).
How does one just build a standard package instead of a meta package? Can't figure it out for life of me. And ARD doesn't like to install/push MetaPackages all that we..
Thanks!
5 replies
Sign in or join Beachball Help to reply.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I haven't seen this problem. Are you sure it isn't creating the new flat packages? I don't remember if the extension for the flat package is mpkg or not. I do know that I have several packages I've built that are plain old pkg files and metapackages, when I want them to be. My minimum OS target is 10.3.9. Could that be the difference?
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I tried your suggestion. When I set the minimum target OS, the package type in the left column changes from "Distribution" to "Mixed," and yet still when I go to build the package it shows up as an mpkg.
I can only get it to make a .pkg when I only have 1 item in the left column under contents. Hmmm...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Templeton Peck wrote:
I tried your suggestion. When I set the minimum target OS, the package type in the left column changes from "Distribution" to "Mixed," and yet still when I go to build the package it shows up as an mpkg.I can only get it to make a .pkg when I only have 1 item in the left column under contents. Hmmm...
Isn't that (more than one part to the package) the definition of a metapackage? If there is one think I learned really early about PackageMaker is that you don't cross it. You have to do it PackageMaker's way, regardless of how silly that way might be. Check out Inno Setup for Windows to see how an installer created is supposed to be like.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
With PackageMacker for Tiger, I had to specifically tell it to create a metapackage, as it viewed those as 1 large package that contained many smaller packages.
Also with PackageMaker for Tiger, I could add as many items I wanted into the PM doc, and it would still stay as a .pkg, so I don't know why the new PM is doing this.
What happens when you start a package from scratch, and add more than one file to it...even if it's just 2 text files?
thanks for your advice so far.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Templeton Peck wrote:
With PackageMacker for Tiger, I had to specifically tell it to create a metapackage, as it viewed those as 1 large package that contained many smaller packages.Also with PackageMaker for Tiger, I could add as many items I wanted into the PM doc, and it would still stay as a .pkg, so I don't know why the new PM is doing this.
It's just flaky, like the rest of the development tools in 10.5.
What happens when you start a package from scratch, and add more than one file to it...even if it's just 2 text files?
I just did a test with two files and it created a .pkg file. I haven't played around with it that much. Once I have it working, I don't mess with it. I have no doubt it can be easily confused.
You can always file a bug report on it when you find a reproducible test case.
On the bright side, the key application is Installer.app. Any program can create a package. If I had more free time that is exactly what I would do.
<Edited by Moderator>