[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-update-dev] Cannot uninstall a feature?
|
The working assumption for update manager
is that features not installed by it are owned by a "native"
installer. Native installers (manual copying falls under that) owns those
features.
In other words, who installs something,
should also uninstall it.
Now, if there is a scheme that assigns
ownership of features to the update manager, than I think your request
would make sense, provided that feature becomes owned by the update manager.
-Dorian
"Brad Jarvinen"
<Brad.Jarvinen@xxxxxxxxxxxxxx>
Sent by: platform-update-dev-admin@xxxxxxxxxxx
02/04/2005 08:44 PM
|
Please respond to
platform-update-dev |
|
|
To
| <platform-update-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [platform-update-dev]
Cannot uninstall a feature? |
|
Would it be a valid feature request
to allow the update manager to manage uninstall of features that are:
1 - not the product feature
2 - are not required by any other
feature that is enabled?
An example I can think of is the
Perforce feature. Let's I install the Perforce feature into my Eclipse
SDK instance by copying it into the features and plugins directory. I
would think that I could uninstall it through the manage configurations
dialog since a) it's not a required product feature, and b) no other feature
I have installed depends on it.
Thanks,
Brad
From: platform-update-dev-admin@xxxxxxxxxxx
[mailto:platform-update-dev-admin@xxxxxxxxxxx] On Behalf Of Dorian
Birsan
Sent: Thursday, February 03, 2005 8:35 PM
To: platform-update-dev@xxxxxxxxxxx
Subject: Re: [platform-update-dev] Cannot uninstall a feature?
Brad, only the features installed by the update manager can be uinstalled
using the update manager.
The eclipse/configuration/org.eclipse.update/registry file keeps track
of this info.
-Dorian
"Brad Jarvinen"
<Brad.Jarvinen@xxxxxxxxxxxxxx>
Sent by: platform-update-dev-admin@xxxxxxxxxxx
02/03/2005 08:59 PM
|
Please respond to
platform-update-dev |
|
|
To
| <platform-update-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [platform-update-dev] Cannot
uninstall a feature? |
|
I'm enabling Update Manager support in our PalmSource Eclipse based product
and ran into something strange. Here's the setup on Eclipse 3.0.1:
I have features A and B. There are unrelated
(no dependencies between them). Feature A is a product feature (aka
primary feature), B is not. If I start eclipse the first time (i.e.
no data in the configuration directory except config.ini), both features
are enabled when I look at the Manage Configuration dialog. But to
my surprise, I can disable B but cannot uninstall feature B (selection
grayed out/not present). I would have thought that as long as it's
not the primary feature and has no other features depending on it, I could
uninstall it.
More testing: I start the product for
the first time with only feature A (the product feature) . I then
later install Feature B through the Update Manager and restart. As
expected, A and B are enabled. When I look at the Manage Configuration
dialog, I see that I can disable B as well as uninstall B. This is
as I would expect. So it seems that if B is present at first startup,
then it cannot be uninstalled at any time later.
To confirm that hypothesis, I then closed
the eclipse instance, deleted the contents of the configuration directory
(except config.ini) and restarted to simulate a "first-time"
start. Both A and B were enabled, and I could not uninstall B, just
like the first scenario I described.
Is this intended? What's the reason
for it? Is there anything I can do about it in config.ini, B's feature.xml,
or any other configuration/metadata file?
Thanks!
Brad
