Hi, It seems "pike -x module spotless" is not so spotless after all. It leaves both "configure" and "autom4te.cache" in the module source directory. Marc
I think that spotless is supposed to leave configure, isn't it? autom4te.cache is cruft left over by newer versions of autoconf. I suppose it might be worth adding that to the makefile. Wonder if it's small enough of a change to get into 7.8 before it goes out the door? Bill On Thu, 9 Oct 2008, Marc Dirix wrote: > Hi, > > It seems "pike -x module spotless" is not so spotless after all. > > It leaves both "configure" and "autom4te.cache" in the module > source directory. > > Marc > >
> I think that spotless is supposed to leave configure, isn't it? I'm not sure about the policy, but configure is generated from configure.in at compile. Marc
My thinking is that configure is something that you'd want to keep for distribution, even though it's a generated file (as there are great differences from one version of autoconf to another). Bill On Thu, 9 Oct 2008, Marc Dirix wrote: >> I think that spotless is supposed to leave configure, isn't it? > > I'm not sure about the policy, but configure is generated from configure.in > at compile. > > > Marc > >
RSS Feed