[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Updates and p2 Install wizard
- From: Susan Franklin McCourt <susan_franklin@xxxxxxxxxx>
- Date: Fri, 21 May 2010 08:48:37 -0700
- Delivered-to: email@example.com
The UI intentionally operates at the level of the "install roots."
So neither install or update would recognize "xyz" has having an update. There is no IU anywhere with an update descriptor for xyz.
If you want to manage updates to abc specifically, you can install it as a root. (ie, select it and install it using the UI). You'll get a message saying that it's already partially installed (or something like that) and it will mark it as a root.
At that point it is separately updatable.
Recall that p2 prior to 3.6 used to give you those "free upgrades" to requirements every time you tried to provision. This was unpopular, unexpected, etc. (esp if you were trying to uninstall something and got a free upgrade to abc while doing so).
So now you aren't getting those free upgrades.
Now that the planner/solver behavior has changed, I think you are right - people might expect what you did. It's like a "deep check for updates".
But the model in the UI right now is...if you care about a feature and its version...install it. If it's just a requirement the requirements will not be upgraded for free because the solver now favors what's installed
Thomas Hallgren ---05/21/2010 02:50:30 AM---Consider the following:
Consider the following:
1. I have a feature xyz version 1.0.0 with a requirement to a bundle abc
2. I install xyz using the p2 install wizard. The resulting install now
contains xyz-1.0.0 and bundle abc-1.7.0.
3. The bundle abc-1.7.1 is published in a repository that is available
My xyz-1.0.0 can now use abc-1.7.1 without modification. Great! This is
one of the key motivators for using version ranges. Unfortunately, p2
seems to lack some support for this in the UI:
4. I go to the install wizard. There is no indication that an update is
available for xyz-1.0.0.
Although disappointing, I can live with it knowing to indicate that p2
must resolve all visible features in order to detected underlying
updates and that would take some time. But what's worse is what happens
5. I check my xyz-1.0.0 anyway and click Next. I get this error message:
Cannot complete the request. See the error log for details.
"Feature xyz" will be ignored because it is already installed.
I know it's installed. I want to update it anyway because I know that
newer content exists that it can make use of. Why am I not allowed to do
that here? Perhaps this is just done when checking if updates are
available? So I try that:
6. I click on "Check of updates..."
I dialog box pops up. "No updates found".
It seems like something is missing because now I'm forced to use the
command line director application to perform my update.
p2-dev mailing list