Re: Installer project directory clarifications
Re: Installer project directory clarifications
- Subject: Re: Installer project directory clarifications
- From: Luke Bellandi <email@hidden>
- Date: Mon, 26 Mar 2007 09:48:41 -0700
Hi Mike & Stéphane,
On Mar 25, 2007, at 11:57 AM, Stéphane Sudre wrote:
On dimanche, mars 25, 2007, at 06:20 PM, Mike wrote:
<snip>
But there's really no interest in creating a package per raw
components (application, associated frameworks, Application Support
sub folder, etc...)
Actually there is. Consider this example:
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:
receipt 1: MySoftware Application v1.0
receipt 2: MySoftware Framework v1.0
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:
receipt 1: MySoftware Application v1.0
receipt 2: MySoftware Framework v1.1
Then 4 weeks later you add a feature to your application, and ship
that as a separate package, you'd end up with:
receipt 1: MySoftware Application v1.1
receipt 2: MySoftware Framework v1.1
If you were to ship the initial software package as one package, you
would have:
receipt 1: MySoftware v1.0
After shipping the framework patch, you'd need an additional receipt,
so you'd have:
receipt 1: MySoftware v1.0
receipt 2: MySoftware Framework Update v1.0
After shipping the updated application, you'd need yet another
receipt, so you'd have:
receipt 1: MySoftware v1.0
receipt 2: MySoftware Framework Update v1.0
receipt 3: MySoftware Application Update v1.0
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.
Best,
Luke
My 0.01503€
_______________________________________________
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
_______________________________________________
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