Do to the upcoming incompatibility of autotools with configure.in, we should start spitting QA warnings when they are used in a buildsystem. Could you please add something to every function from the eclass which interacts with configure.in? This will hopefully limit the breakage which will come
In that case we might as well do a blanket mv configure.{in,ac} and *then* warn about it? Also, in subdirs? :)
*** This bug has been marked as a duplicate of bug 426262 ***