Packagemaker 3.0: Do I need specify Package Identifier for EACH component?

Andrey Kaplunenko wrote:
I'm learning how to make packages for software distributions. I'm using *Packagemaker 3.0* and found out one problem.

Only one?

But that's silly! Why installing too much trash? What if application has 100 components?

You will get 100 receipts. I've seen one big program that did that. Perhaps it was Office. I don't remember.

I have not found any helpful info in PM documentation...

I don't doubt it.

I noticed that two of your components are both Perian installed into /Library. You could bundle those up into one. Theoretically, you could bundle everything up into one component and install it into /. The only real reason you would need to split up components is if you need to control them separately.

I wouldn't recommend that. You should really play by PackageMaker's rules. Of course, those rules aren't written down anywhere 🙂

What you can do is set your destination to be just / - nothing else. Then, the files that you install need to have their own, correct, hierarchy. You start with a temp folder. In that temp folder and create the following hierarchcy (for example): /tmp/packagemaker/Library/QuickTime/Perian. Then, you build your package using /tmp/packagemaker. I have scripts that build my temp directories just so before I ever start PackageMaker. Next, apply the appropriate (usually root) permissions to your temp files. (This way, you can keep non-root files in your own SCM repository). Finally, build the package using those temp files. Depending on how you structure your hierarchy, you may need to check/uncheck "Include root in package".

I've made it sound easier than it is. There is some trial an error involved.

Let me know if this doesn't make sense. I know it is confusing.

Click the "Contents" tab and uncheck "Include Root in package"