[Rake-devel] Removing ENV from the Task Argument Lookup Process

[Bennett, Patrick]

I heavily rely on users being able to specify environment variable overrides (or 'defaults' more often) for command-line arguments.
I'm referring to generic XXX=1 type stuff on the command line.  If that doesn't apply to task specific arguments then I don't (personally) care.

Patrick

On Dec 28, 2009, at 6:13 PM, Jim Weirich wrote:

> I have received a suggestion to remove checking the environment for  
> the value of a task argument.  For example, given:
> 
>    task :sample, [:path] do |task, args|
>      puts args.path
>    end
> 
> will print out the value of the environment variable PATH.  The  
> requester comments that the feature can cause bugs that are difficult  
> to track down.  Upon reviewing his comment, I tend to agree with him.
> 
> So, is anyone taking advantage of this feature?  Would anyone be upset  
> if we remove it?
>