1 |
Eivind Tagseth kirjoitti: |
2 |
> Jean-Noël Rivasseau wrote: |
3 |
>> 2) It would have a simpler configuration syntax (pure familiar Bash |
4 |
>> syntax resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the |
5 |
>> syntax in the eclipse.ini file is more obscure even for me - looks |
6 |
>> like there should be one option per line). |
7 |
>> |
8 |
>> What is your feedback on this? Other options could include sourcing |
9 |
>> ~/.eclipserc, I don't like that much (it would create yet another .* |
10 |
>> file in the home directory). Plus this is probably something to set |
11 |
>> globally on the system. |
12 |
>> |
13 |
>> However, I was wondering if /etc/conf.d would be appropriate for an |
14 |
>> application's settings. Most of the stuff there is either server |
15 |
>> related (tomcat, apache etc...) or system related (alsa, clock, xdm...) |
16 |
>> |
17 |
> How about an environment variable like ECLIPSE_MAX_MEMORY (or |
18 |
> ECLIPSE_JAVA_OPTS) that's put in a file in /etc/profile.d? |
19 |
> |
20 |
> This would let administrators set up good system defaults, while |
21 |
> allowing users to override the settings in their own shell (command |
22 |
> line, og .bashrc etc). |
23 |
> |
24 |
> |
25 |
> Eivind |
26 |
|
27 |
Environment variables would work but for example Debian has a strict |
28 |
policy against environment variable pollution. /etc/conf.d/ is not |
29 |
really meant for applications. I would suggest using .gentoo/eclipserc |
30 |
because that would avoid possible problems with upstream adding |
31 |
something like .eclipserc in the future. |
32 |
|
33 |
Regards, |
34 |
Petteri |