On Wednesday 04 December 2002 01:06 pm, you wrote: > > I basically see three camps in this discussion: > > 1. Users should be able to configure default behavior using configuration > files (which would be selected based on argv[0] or similar) > > 2. Users should be able to configure default behavior using environment > variables (which would be configured on a per-application basis using > wrapper scripts or a launcher program or similar) > > 3. Users should not be able to configure default behavior; applications > should specify all behavior explicitly if it matters, and expose this as an > application-level configuration option to the user
It seems to me that 2 and 3 are independent. I don't see why the application's configuration doesn't just provide an interface to changing it's own environment variables. This would allow wrapper scripts to supply variables/values the application didn't know about when written, and let the application provide a nice interface to the user for changing them as well. Wrapper scripts can provide both default settings (bashrc) or per-application settings just the same. It seems as if none of the levels of controls people have been asking for in this thread can't be satisfied via environment variables in one way or another--it seems to be the most flexible solution. Nick ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
