[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] How to build an update site for a product?
- From: Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 9 Sep 2010 09:13:53 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=Mhr+uzmuT1Dh6TKFM6mlssSXAq3Ch5fkHRAf2ZuEd01fym5tZIYL6pbckYwOXCzmbM udffTwQc6FV5ZRYDJEaAGRApwYw2JGY2SkqoLfUtuiUir5aGHQzAeYZUXR/c2SJge8bt xGQciTof3ITl1nRZxvxFeLmzPUdHCtVt16Qbk=
On Thu, Sep 9, 2010 at 8:39 AM, Samuel Wu <samuelwu@xxxxxxxxxx> wrote:
> Thank you for the suggestion, Michael. I understand that the features included in a product can't be updated without updating the product itself and I've set up something similar to yours to work around this issue.
A product can be composed in such a way that some features are
updateable independently of the product (it's similar to what's
described here, but deliberate). You can also take the features of
the product and "re-install" them, making them available as root IUs
makes them updateable.
Hi floor.Â Make me a sammich! - GIR