[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse-dev] Planning Meeting Notes - Nov 12, 2003
- From: Jan Schulz <jasc@xxxxxxx>
- Date: Sat, 15 Nov 2003 16:58:28 +0100
- Delivered-to: email@example.com
- User-agent: Opera7.21/Win32 M2 build 3218
* Peter Manahan <manahan@xxxxxxxxxx> wrote:
I am not sure I understand what all the fuss is about. The .config dir
not user information. It is eclipse system configuration. Allowing
users to modify that is like allowing just anyone to write to the /etc
In config is the infortmation, what 'sites' are installed. If that's saved
/etc, it means that users cannot specify a plugin dir relative to "$HOME".
.config is actually not something, which belongs to /etc, as it is
initialized by the programm and not by the admin (or package
1) root installs eclipse and in that process creates the .config via
eclipse -initialize -data /tmp/workspace
2) user runs eclipse without error.
for purists this is supposed to work (requires a wrapped eclipse
Fun. Now considere a university, where the admin isntalls eclipse. Now a
wants to install a new plugin.
1) root install of eclipse
2) root then creates the .config in say /etc/eclipse/.config using the
-configuration flag "eclipse -initialize -data /tmp/workspace/
3) user runs without error using the eclipse -configuration /etc/eclipse/
So I will change my wrapper script in the enxt version, depending, what is
actually written by initialize. AFAIK, Mozilla has something similar:
registry. AFAIK, this goes to /usr/share. This app is run after every
of a mozilla plugin/component
A /etc file would be something like the 'links/*links files or a config
which specifes the default window system.
What eclipse is missing is the user portion of this which right now is
per workspace rather than per user.
Yes, that is missing too.