Re: [platform-update-dev] Install configuration location

[Pat McCarthy <patmc@xxxxxxxxxx>]

Can this be something that is defined in the install.ini (currently or in the future)?

This might let branded launch points define the config location such that the user does not need to specify the option at all.  

With a common config location, soft installs (using only update manager) would no longer be workspace specific when the target is other than the current products /eclipse directory.

Along the same line of thought, I've been considering a request for a common/default target for update manager installs such that it is other than the product's /eclipse directory.  The colocation-affinity can force an update to a specific location, but if we could force a new install via Update Manager to a known location this might prove to be easier to manage for product teams and users alike.

Regards,

Pat McCarthy