| Summary: | [director] Install categories same from the director / UI | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Daniel Jacobowitz <dan> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | pascal, thomas |
| Version: | 3.5 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Daniel Jacobowitz
This code leaves in the org.eclipse.equinox.p2.director.app bundle, class DirectorApplication. If you are willing to take a look at patch this would be really great. Just my opinion, but I think it shouldn't be new code in the director. I recently wanted to do some operations I couldn't do from the director and wrote another application to invoke p2 APIs; the smarter the director (rather than the core / engine) is, the harder it is to use the core / engine. Just to be sure I understand, are you suggesting that you would see this kind of behavior to be added to the planner (or closer to the core) rather than in higher levels? Yes, I think so - either the planner, or e.g. ProfileChangeRequest#addInstallableUnits. Now I'm concerned. I use the planner in aggregation situations to verify and determine what IU's to include in an aggregated result repository. I depend on that the planner includes the categories in that result. If the planner is changed, then that code needs to be changed too. IMHO, when coding for P2 there are enough exceptions created by the current category concept already. Please don't add more. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |