1 |
Jean-Noël Rivasseau wrote: |
2 |
> 2) It would have a simpler configuration syntax (pure familiar Bash |
3 |
> syntax resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the |
4 |
> syntax in the eclipse.ini file is more obscure even for me - looks |
5 |
> like there should be one option per line). |
6 |
> |
7 |
> What is your feedback on this? Other options could include sourcing |
8 |
> ~/.eclipserc, I don't like that much (it would create yet another .* |
9 |
> file in the home directory). Plus this is probably something to set |
10 |
> globally on the system. |
11 |
> |
12 |
> However, I was wondering if /etc/conf.d would be appropriate for an |
13 |
> application's settings. Most of the stuff there is either server |
14 |
> related (tomcat, apache etc...) or system related (alsa, clock, xdm...) |
15 |
> |
16 |
How about an environment variable like ECLIPSE_MAX_MEMORY (or |
17 |
ECLIPSE_JAVA_OPTS) that's put in a file in /etc/profile.d? |
18 |
|
19 |
This would let administrators set up good system defaults, while |
20 |
allowing users to override the settings in their own shell (command |
21 |
line, og .bashrc etc). |
22 |
|
23 |
|
24 |
Eivind |
25 |
-- |
26 |
gentoo-java@l.g.o mailing list |