[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] Updates and p2 Install wizard

Well, it would be a lot more useful if there is a UI, but I was thinking in direction to find a workaround for Thomas's case. 
Taylor, my idea was similar to your proposal:) But instead of playing with the feature, we can decouple xyz and abc ( we can wrap the bundle into a new feature).
In both cases you need to have access to the repository, of course. 

In an ideal case the UI may provide list of all (transitive) dependencies which your bundle relies on and you can choose which of them to be explicitly updated. 
Otherwise, especially in cases of deep hierarchy, a lot of unnecessary updates would be performed. 
 
Kind regards,
Katya

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Taylor, Richard
Sent: Friday, May 21, 2010 3:02 PM
To: P2 developer discussions
Subject: RE: [p2-dev] Updates and p2 Install wizard

Is there a simple solution ala:
  Define the 1.7.0 feature to require bundle abc-[1.7.0, 1.7.0)
  When the abc-1.7.1 bundle becomes available, build another feature
1.7.1 that requires bundled abc-[1.7.1, 1.7.1)

With a little luck the 1.7.1 feature will be seen as an upgrade to the
1.7.0 and the update will take place.

Regards,
Rick



The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
Behalf Of Thomas Hallgren
Sent: Friday, May 21, 2010 7:52 AM
To: p2-dev@xxxxxxxxxxx
Subject: Re: [p2-dev] Updates and p2 Install wizard

Hi Katya,

Perhaps I was unclear about the point I was trying to make. I'm fully 
aware what can and cannot be done with the p2 infrastructure and with 
the director application. My concern is that the user interface has no 
support for use cases that I think is becoming increasingly common.

More comments inline:

On 05/21/2010 01:10 PM, Todorova, Katya wrote:
> Hi Thomas,
>
> You cannot update your feature xyz (and you get "no update found"
message), because it has the same version as in the repository.
> P2 downloads all necessary "requirements" when you install your
feature, but I don't think that it should check whether these
requirements are updated and download these updates on feature update.
>    
If I install something today, and and then create another installation 
tomorrow (using the exact same feature version), the second installation

might be different since newer bundles are available. So far so good. 
What really bugs me is that there's no way for me to bring my first 
installation up-to-date with the second. There should be a way to ask p2

to do that (from the UI).

> Since the feature does not explicitly requires the new version of abc
bundle, it is considered as "up-to-date". Satisfied dependencies of the
feature are not forcefully updated when a new version of abc comes -
> this is the same behaivior as described in OSGi spec for bundles.
>    
I don't want any forceful update. I just want p2 to update when I 
explicitly tell it to. As it is right now there's just no way for me to 
make that happen. Well, short of actually uninstalling the feature first

and then reinstall the exact same version again.

> What you could do is explicitly download abc bundle before downloading
the feature - thus you'll have the possibility to update abc
independently from your feature and use whatever vesion of abc you want.
>
>    
No, I can't do that because there's no user interface to support it. The

bundles are never exposed in a way that enables me to select them for 
update.

Regards,
Thomas Hallgren


> I hope that helps.
>
> Kind regards,
> Katya
>
>
>
>
> -----Original Message-----
> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
On Behalf Of Thomas Hallgren
> Sent: Friday, May 21, 2010 12:50 PM
> To: P2 developer discussions
> Subject: [p2-dev] Updates and p2 Install wizard
>
> Consider the following:
>
> 1. I have a feature xyz version 1.0.0 with a requirement to a bundle
abc
> [1.7.0,2.0.0).
> 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
> to me.
>
> 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
> next:
>
> 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.
>
> - thomas
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>    

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev