[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Install configuration location
|
I would be careful when bending Update Manager just enough to address an
immediate problem when the real problem requires a more through redesign.
We are in the 3.0 mode now and we would rather look at the bottom of the
matter first, then address it in a way that does not feel like a hack. Your
suggestions implies that the problem is in the space of corporate 'push'
update scenario. I would like to explore this space more and get a feeling
of the problems we are trying to solve before recommending a solution. If
that solution implies writing new code and using things other than Update
Manager, so be it.
Regards,
Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745 T/L 969-2745
Fax. 905 413-4854
Pat
McCarthy/Raleigh/IBM@IBMUS To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@ Subject: Re: [platform-update-dev] Install configuration location
eclipse.org
05/15/2003 10:35 AM
Please respond to
platform-update-dev
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
