Eivind Tagseth kirjoitti:
> Jean-Noël Rivasseau wrote:
>> 2) It would have a simpler configuration syntax (pure familiar Bash 
>> syntax resulting in things like ECLIPSE_MAX_MEMORY="128M", whereas the 
>> syntax in the eclipse.ini file is more obscure even for me - looks 
>> like there should be one option per line).
>>
>> What is your feedback on this? Other options could include sourcing 
>> ~/.eclipserc, I don't like that much (it would create yet another .* 
>> file in the home directory). Plus this is probably something to set 
>> globally on the system.
>>
>> However, I was wondering if /etc/conf.d would be appropriate for an 
>> application's settings. Most of the stuff there is either server 
>> related (tomcat, apache etc...) or system related (alsa, clock, xdm...)
>>
> How about an environment variable like ECLIPSE_MAX_MEMORY (or 
> ECLIPSE_JAVA_OPTS) that's put in a file in /etc/profile.d?
> 
> This would let administrators set up good system defaults, while 
> allowing users to override the settings in their own shell (command 
> line, og .bashrc etc).
> 
> 
> Eivind

Environment variables would work but for example Debian has a strict 
policy against environment variable pollution. /etc/conf.d/ is not 
really meant for applications. I would suggest using .gentoo/eclipserc 
because that would avoid possible problems with upstream adding 
something like .eclipserc in the future.

Regards,
Petteri