[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-update-dev] Question about update on multi-user systems
|
When you say "mark the eclipse install as read only," are you talking
about a setting within Eclipse or on the filesystem itself?
If within Eclipse, I was not aware of this feature, and even after
looking I couldn't find it. I'm using 3.2M5 also.
If on the filesystem, that is how my system is set up, but I don't get
the option to install in a different location; I just get a general
install failure (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=133036 for
details).
Maybe it works differently on Linux than Windows???
>>> On Tue, Mar 28, 2006 at 7:25 AM, in message
<OF3EC69B6A.FF43019B-ON8525713F.004E6F4C-8525713F.004F3B47@xxxxxxxxxx>,
Pascal
Rapicault <Pascal_Rapicault@xxxxxxxxxx> wrote:
> This scenario used to work in 3.1 and still works in 3.2 (I just
tested it
> with 3.2 M5a).
> The best way to setup this type of install is to mark the eclipse
install
> as read only. This will cause the configuration location to be set to
the
> user home directory, which will cause isolation between the shared
install
> and the user install.
> When the user will download plug- ins through update, he will be
asked to
> choose a folder where to download the plug- ins since the shared
install
> location is read only.
>
> PaScaL
>
>
>
>
> Jeff McAffer/Ottawa/IBM@IBMCA
> Sent by: platform- update- dev- bounces@xxxxxxxxxxx
> 03/28/2006 09:01 AM
> Please respond to
> "Eclipse Platform Update component developers list."
>
>
> To
> "Eclipse Platform Update component developers list."
> <platform- update- dev@xxxxxxxxxxx>
> cc
>
> Subject
> Re: [platform- update- dev] Question about update on multi- user
systems
>
>
>
>
>
>
>
> Matt,
>
> This is an excellent usecase and would be very interesting to
support.
> Mechanically we are there today but the workflow is likely less than
> optimal. When you run Eclipse you run "configurations" (or lists) of
> plugins. These can be in many different locations. If each user has
> their own configuration (read list) then they are free to update it
as
> they choose. They can then of course download/install new features
to
> their configuration and place them where they want. We have a notion
of
> shared or parented configurations that is intended to play in this
area
> but has not been driven home throughout Update. Under this model
there is
> one central configuraiton and each user configuration adds some
> information and points to the shared one for the defaults.
>
> Could you open a bug report detailing the usecase (as you did below)
so
> what we don't lose the information or forget?
>
> Jeff
>
>
> "Matt Ryan" <mryan@xxxxxxxxxx>
> Sent by: platform- update- dev- bounces@xxxxxxxxxxx
> 03/21/2006 10:27 AM
>
> Please respond to
> "Eclipse Platform Update component developers list."
>
>
> To
> <platform- update- dev@xxxxxxxxxxx>
> cc
>
> Subject
> [platform- update- dev] Question about update on multi- user systems
>
>
>
>
>
>
>
>
> Hello,
>
> I have a question about Eclipse update on multi- user systems, like
Linux.
>
> The essence of the question is this: As we know, Eclipse comes with
a
> built- in update mechanism. There is also the ability to set up
extension
> locations, additional places where Eclipse looks for plugins.
> My question: Has there been any consideration to tying some of this
> functionality together so that users of Eclipse on a multi- user
system can
> use the update mechanism to install plugins without effecting the
system
> installation?
>
> Here's a typical use case on Linux. Eclipse on Linux may be
installed in
> a centralized location (/usr/share/eclipse on our SUSE Linux
platform)
> instead of inside a user's home directory. This way, every user on
the
> system can run Eclipse from that one installation. However, this
poses
> two problems. 1) Most users may not have appropriate permission to
write
> to the installation location, so Eclipse update will not work for
them. 2)
> Even if they can write there, they may not want to because perhaps
not
> every user on the system wants to have the same plugins. 3) The
extension
> location option is available to them, but this is not user- specific
-
> meaning, Eclipse doesn't use different extension locations for
different
> users running on the same system (or if it does I missed it
somehow).
>
> What are your thoughts on this?
>
>