Re: [platform-update-dev] eclipse installation site types cleanup

[Dorian Birsan <birsan@xxxxxxxxxx>]

-Dorian


platform-update-dev-admin@xxxxxxxxxxx wrote on 04/12/2004
03:48:56 PM:

> Hello Dorian,
> 
> Monday, April 12, 2004, 8:46:49 PM, you wrote:
> > - for consistency with the path specified in a .link file, the
add site
> > dialog should allow selecting the actual product extension (i.e.
the 
> > folder containing the eclipse directory), as opposed to having
to select 
> > the eclipse folder itself as done now. Also, when creating a
site in the 
> > install wizard, instead of creating features and plugins folders
inside 
> > the selected location, create an eclipse parent directory first.
> 
> I would like to suggest the other way around: make selecting the
> right dir possible. It's just a waste of path elements to add a
> $HOME/.eclipse/eclipse/{plugins,features} path, only to hide it in
> your home dir. I would rather use
> $HOME/.eclipseextention/{plugins,features}.

I too like this approach, but it breaks the 2.x specs.
It appears that having an eclipse folder leaves some room for things other
than features and plugins (at least that's one of the explanations I've
heard).

> 
> Another nice feature would be a 'root only updates', so that one
> could update the site via the commandline updater, but not via the
> normal user UI.

You can already do this by having a shared install,
and linking product extenstions using the "r" flag
path=r /home/rootinstall
Do you have a different usage scenario?

> 
> Jan, debian eclipse maintainer
> 
> _______________________________________________
> platform-update-dev mailing list
> platform-update-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-update-dev