| Summary: | [eclipse] product id not cleared on uninstall | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | DJ Houghton <dj.houghton> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | dstevens, jeffmcaffer, pascal.rapicault, pascal |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
DJ Houghton
The problem probably comes from the metadata that does not unset the product settings. However if we had that ability, then we would have no product in the config.ini which is not really better. It seems that the right solution is to have the metadata to unset and have the engine run a "re configure" phase on the IUs that are left in the system. What are you using the QAContact for? I don't recall us using this field before? I meant to use the CC field :) still an interesting problem. in the case of uninstalling the thing the currently supplies "productness", it is ambiguous what the new product should. In the case of an undo, we can revert to the previous product. In the plain uninstall case we need to be told or something. to be told, we likely need to ask. to ask, we need to give the user some choices. to give choices we need to know what things would be reasonable choices. (and so on...) We had similar problems in the past with our RPM packages. We try to mirror the upstream SDK downloads so we have eclipse-rcp and eclipse-platform and eclipse-sdk (among others). The problem we ran into was when we were shipping a configuration so that config.ini needed to be changed on an installation of eclipse-sdk if eclipse-platform was already installed. Now we just don't ship a system-wide configuration and let each user get a generated one :) Just trying to clear the QA Contact for bug 199090 We need to make the action smarter. |