site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi Mike & Stéphane, On dimanche, mars 25, 2007, at 06:20 PM, Mike wrote: <snip> Actually there is. Consider this example: receipt 1: MySoftware Application v1.0 receipt 2: MySoftware Framework v1.0 receipt 1: MySoftware Application v1.0 receipt 2: MySoftware Framework v1.1 receipt 1: MySoftware Application v1.1 receipt 2: MySoftware Framework v1.1 receipt 1: MySoftware v1.0 receipt 1: MySoftware v1.0 receipt 2: MySoftware Framework Update v1.0 receipt 1: MySoftware v1.0 receipt 2: MySoftware Framework Update v1.0 receipt 3: MySoftware Application Update v1.0 Best, Luke My 0.01503€ _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/luke%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... On Mar 25, 2007, at 11:57 AM, Stéphane Sudre wrote: But there's really no interest in creating a package per raw components (application, associated frameworks, Application Support sub folder, etc...) Let's say you're shipping a product that has an application and a framework. You make 2 packages, one with the application and one with the framework. You then make a distribution that installs both bundles. Up to this point, this is functionally equivalent to putting everything in one package, except that you will have two receipts: 2 weeks later you realize there's a bug in your framework, so you want to ship a fix for it. Since you shipped two packages in the original case, you can ship an update package with just the framework. It will upgrade the framework and leave the application alone, so your receipts will look like: Then 4 weeks later you add a feature to your application, and ship that as a separate package, you'd end up with: If you were to ship the initial software package as one package, you would have: After shipping the framework patch, you'd need an additional receipt, so you'd have: After shipping the updated application, you'd need yet another receipt, so you'd have: As you can see, method 2 gets messier as time goes on and you ship updates to your software's components. I'd suggest you spend some time considering what the most logical divisions in your software product are, and create individual software packages along those lines. It will make life much easier for you as you ship updates to your software. This email sent to luke@apple.com This email sent to site_archiver@lists.apple.com