|Re: [equinox-dev] [prov] p2 filtering|
Hi, Helmut. I'll take a stab at these, although I don't know about #3.
1) First ask the user what hosts/archs etc. he
wants to install and then use that information in both the UI and the
installation itself. Is this possible at all?
The specific notion of considering the profile values for filtering is discussed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=225365.
Also, I'm working now on bug #216028, which provides alternate presentations of the available IU list (flat/by site/by category). To achieve this, I needed additional context, also. What I've done (not released yet) is add the notion of a QueryContext that can be set on any QueriedElement. The QueryContext can be used to determine what the exact query type should be, and in addition, the IQueryProvider can access it while building the query. For example, both the category and flat view are query type of AVAILABLE_IUS, but now the query provider and look into the query context and see if there is more info regarding grouping or filtering. Clients can install the context they want on the model elements. So..conceivably, if we don't yet implement profile-based filtering, this is something you could add by installing a query context into the elements.
2) Can a profile have multiple values for the same property?
I don't think so, someone please correct me if I'm wrong about this.
2.1) Profiels.getParent(): I've seen the concept of child/parent
profiles, this might help answer question #2,
This is really a placeholder concept based on experience with products in the provisioning space. Right now, p2 doesn't use it as a base level, but when the requirements were being discussed, this was an important concept in some installations.
4) I managed to get a lot of IStatus.ERROR in my ProvisionPlan, is checking
the plan for errors the right way to look at the sanity of the set of
IUs I want to install?
Yes, an ERROR status on the plan means that the plan will not work. an OK means it will. With other status severities in between (INFO, WARNING), it's possible to pass the plan to the engine and something will happen (depending on the code/nature of the status.) Right now in the SDK UI, we do not let the user try a plan if it is not OK. In the Admin UI, we have a preference that allows users to try non-OK plans anyway. This would be up to your UI.
"Haigermoser, Helmut" <Helmut.Haigermoser@xxxxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
04/03/2008 12:57 AM
Subject: [equinox-dev] [prov] p2 filtering