Re: [platform-update-dev] Re: Update Manager Installs - Forcing the Use

[Peter Manahan <manahan@xxxxxxxxxx>]

We may be actually in agreement. I only
really have one issue with with after reading it over again and reading
this. And that is the contraints placed on the default path need to be
set.

platform-update-dev-admin@xxxxxxxxxxx wrote on 21/04/2004
02:06:15 PM:
 
> 
> Peter,
> 
> We are in no way trying to duplicate a native installer.  We
are, however
> (as I said) taking a hint or two from them.  It is foolish to
ignore
> lessons learned there.

Yep no question there.

> 
> There are specific usecases that occur in both worlds and the one
we are
> concerned about here is pretty fundamental:  Installing a new
feature for
> the first time.  Where do you put it?

Wherever the native installer puts it in my case.
In the general eclipse case in the eclipse directory. 

> 
> The body of native installers have a compelling convention of offering
a
> default path suggested by the vendor that the user can choose to override.
> 

Default path suggestted by the os vendor yes. So the
current default path for eclipse (as the os vendor for the eclipse platform)
is the main eclipse directory. I am not saying that it is the best default
path or it shouldn't change just that that directory should not exist outside
of the eclipse domain (its directory structure). So if eclipse ships an
eclipse\extensions directory that the update manager sets as the default
install directory for new features thats great. Create as many extension
subdirs under there as needed. Eclipse owns that area. 

I only have an issue with allowing eclipse to target
directories outside the main eclipse directory that it owns. 
 
> This sort of thing is not a hack in any way.  This is an extremely
> important feature as it directly impacts useability and serviceability.
> 

I agree that it is an important feature I just don't
agree that the implementation of it in eclipse should allow eclipse to
retarget the filesystem outside the eclipse directory. That what crosses
the line into it becoming a native installer. So easy to stray to the dark
side.

> I am definitely familiar with thinking of Eclipse as an applications
> platform.  Are you familiar with what we are doing with it in
our team?  If
> not feel free to contact me off-list.
> 
> Cheers,
> 
> Mel
> 
> Dr. Mel Martinez
> IBM Rich Client Platform
> melm@xxxxxxxxxx
> 


Thanks,

-----------------------------------
Peter Manahan
IBM Rational Tools
Common Install
------------------------------------
manahan@xxxxxxxxxx