On Dec 10, 2010, at 12:26 AM, Dimitri Fontaine wrote:
> What if $extension.control exists? Is it a byproduct of the .in file
> from previous `make` run or a user file? What if we have both the .in
> and the make variable because people are confused? Or both the make
> variables and a .control and not .control.in? Etc...
There are ways to deal with those issue, I'm sure.
>> * Always remove $extension.control in the `clean` targets
>
> Hell no, as you can bypass the .in mechanism and provide directly the
> .control file.
I'm saying disallow the .control file, only allow the control.in file.
David
