[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Promoting a sub-feature to a root feature
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Fri, 06 Jan 2012 16:08:46 +0100
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20110928 Fedora/3.1.15-1.fc14 Lightning/1.0b2 Thunderbird/3.1.15
For those interested in how this problem was finally resolved, have a look at this issue:
Thanks to everyone that helped with ideas and thoughts around this.
On 2012-01-05 14:10, Thomas Hallgren wrote:
The problem is as follows:
Feature A includes feature B. This means that B cannot be uninstalled even if B is optional.
The solution for us is to change A to no longer include B. When we package our product, we instead install B using the
p2.director. This means that both A and B become root IU's and be managed individually. But now the shit hits the fan.
When our users update their products instead of downloading a new packaged product, A is updated and B gets
uninstalled. I know, this is to be expected and it's the correct behavior from p2, there's no doubt about that. But
what can be done to prevent it? What we really want is:
A is updated to no longer include B
B is kept and promoted to a root
Is there anyway we can accomplish this?
p2-dev mailing list