Under windows and possibly also Linux the configure extensions installer fails or at least warns about unsafe files.

The problem is that the filter is too hard and see files with , as unsafe. The ,v files creates warnings for this reason when they are there for some reason (happens in many extensions).

Also the warning message is useless to developers because it fails to say WHICH file is unsafe.

So a $f in the message will help a lot.

Checking in fix

• KennethLavrsen - 31 Dec 2008

Per Sven's advice the $f can stop program execusion because it is tainted.

So I remove this part of the fix. I may later return with a more elegant solution that encodes the filename and untaints a copy of the variable for display. But no time for this now. it is not important because we should really never see this message in practical.

• KennethLavrsen - 01 Jan 2009