
On 11/22/2011 1:46 PM, Ruediger Meier wrote:
On Tuesday 22 November 2011, Cristian Rodríguez wrote:
On 22/11/11 15:18, Ruediger Meier wrote:
Ah you are right! I see bashrc and the whole stuff in profile.d/, bash_completion.d/ is misused too.
We are talking about sysconfig implementation and purpose, not about shell profiles ! come on !
It doesn't change the fact there it's nothing bad with using shell code within config files if you know they are interpreted by shell.
It is in fact an explicit feature. Not some abused accident. It is the very reason things are done that way when & where they are, barring plainly bad coding by the inexperienced. If you intend a file to contain only some key/value pairs, you write them in a file that doesn't even pretend or accidentally look like a shell (or other) script, and you do not read that file by sourcing it with any script interpreter. If you DO read a config file by sourcing it right into your current interpreter, then by definition you INTEND for that config file to contain ANYTHING that your script interpreter can do, including sourcing yet other files and running other programs. This allows function libraries, modular chunks of common shared configs, dynamic configs, gah it's endless. Good grief the wrongness of this argument is beyond laughable. This modularity and tool-combining functionality and "we don't know or care what use you might make of this, we're just providing an unlimited flexible blank slate with a bag of small tools you assemble any way you discover you need to, with merely some convention as a helpful starter and guide, instead of trying and failing to predict every possible legitimate need that ever might come up in the future by anyone anywhere ever" is part of the very dna of unix from day one.
"no shebang => no script" is simply wrong.
There are better examples than shell profiles of course. Some of them using python, others using lisp or whatever and sysconfig is currently using shell.
Anyway.
cu, Rudi
-- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org