[platform-update-dev] Shared vs. per-user configuration consistency

[Brian Eliot <beliot@xxxxxxxxxx>]

When a per-user configuration is created (e.g., in $HOME/.eclipse)
it is linked to the shared configuration in the product install
location.  If the shared configuration is subsequently invalidated,
say through a product removal/re-install cycle, the per-user
configuration appears to remain intact, generally resulting in
runtime exceptions when launching the workbench as that user, until
the per-user configuration is forcibly removed (either the entire
configuration/ directory or at least platform.xml).  It would be
difficult for an installer to find and invalidate all these
separate configurations when replacing the product.

Is there any detection that the shared configuration link from
config.ini is out of date, and if not, is there a clean way to
force the per-user configuration to be refreshed?  Neither the
-initialize or -clean options appear to have any effect.  The
working assumption is that if the product install location has
been completely recreated, any preexisting feature configuration
for this user is automatically invalid and does not need to be
preserved.
---
Brian Eliot
MontaVista Software, Inc.