Milter-greylist

> ah, i didn't even think about that.  i'm not sure i see the purpose of a
> spec.in file.  if you're using rpm, you aren't going to run configure
> first.  you just grab the spec and tar file and go.  but i know there is
> some rpmbuild option that starts from just a tar file, but i have never
> used that method.  i would guess it just uses the .spec file as well.  can
> anyone else speak to this?

i just did some testing with rpmbuild -t and it just grabs the .spec file 
from inside the tarball and uses it directly.  so i think that having a 
spec.in file is probably not very useful.  if you used it in your process 
for building a tarball, that would be ok, but having the spec.in flow 
through to the user doesn't seem to add any benefit.  and all that is 
different between the files is @PACKAGE_VERSION@ vs 4.1.6 so the patch 
works for both files.