GNUSTEP_USER_CONFIG problem (Windows)

[Lloyd Dupont]

(Remark: Richard, I haven't yet investigate your answer but here is another 
problem).

Im trying to use the GUSTEP_USER_CONFIG env var in my deployment scenarion.
The fact is: using environment variable is inapropriate.

=== Because ==
1. if I put the env var in the system settings it's quite possible user 
screw up everything by modifying env are (either accidentally (because of an 
other app?) or on purpose)
2. I can't set the environment variable in the app shortcut
============

So I don't set-up any environment variable but in my application's main() 
function I "try" to setup the environment like that:

char** env = { "GNUSTEP_CONFIG_FILE=F:/lilou", NULL };
[NSProcessInfo initializeWithArguments: argv
                                 count: argc
                           environment: env];

It used to work (for GNUSTEP_SYSTEM_ROOT)
It's not working!
What's that!
What should I do!

It really drives me mad...
Isn't there a (C/programatic) variable somewhere I could edit (like the 
NSLog_printf_handler or NSException_handler).
Instead on relying on environment variable kind of hack which stop to work 
(silently) after a few version?

in fact is there a programatic way of accessing this parameters!

I'm over fed-up with environment variable.
When an environment stop working (because of new developement) nothing warn 
the developer (I mean the compiler don't know). Its application simply stop 
working without warning, without message, without cause.

I think I could safely say now that environment variable are inherently evil 
and should not be the only configuration method. A programatic interface 
should exist to fix any problem!
In this case a programatic way to set GNUSTEP_CONFIG_FILE.


Arrgglll...