I'm wanting to finalize 1.2.1, and don't want to have busted RPM packaging.

Shown below is how the latest patch (which Devrim seemed to have a bit
of an issue with) affects the build (after running configure).

The only thing that appears potentially controversial is the change in
name, from "slony1" to "postgresql-slony1-engine".  If I understand the
way RPMs are processed (and I have built a few RPMs over the years,
albeit before they added the "rpmbuild" program), it *could* be
necessary to change the name there before running "rpmbuild -ba". 

I don't see that 1 line change being something that would cause a big
problem if we had the wrong value in 1.2.1; you'll be building the
packages afterwards, anyways.

At any rate, I'll not be building tarballs until this afternoon, so
there's still some time for comment...

cbbrowne at dba2:~/Slony-I/slony1-HEAD-pristine> diff
postgresql-slony1-engine.spec postgresql-slony1-engine.spec.latest     
Wednesday 15:56:52
9c9
< Name:           slony1
---
> Name:           postgresql-slony1-engine
16c16
< Source0:        slony1-%{version}.tar.gz
---
> Source0:        slony1-%{version}.tar.bz2
47c47
< The slony1-docs package includes some documentation for Slony-I.
---
> The %{name}-docs package includes some documentation for Slony-I.
68c68
<         --with-docs --with-docdir=/usr/share/doc \
---
>         --with-docs --with-docdir=%{_docdir}/%{name}-%{version} \
98c98
< install -m 0644 altperl/slon-tools 
$RPM_BUILD_ROOT%{_libdir}/pgsql/slon-tools
---
> install -m 0644 altperl/slon-tools 
$RPM_BUILD_ROOT%{_libdir}/pgsql/slon-tools.pm
103a104
> /bin/rm -f $RPM_BUILD_ROOT%{_bindir}/pgsql/slon-tools
111c112
< %doc COPYRIGHT UPGRADING HISTORY-1.1 INSTALL SAMPLE RELEASE-1.1.5
---
> %doc COPYRIGHT UPGRADING HISTORY-1.1 INSTALL SAMPLE RELEASE-%{version}
121c122
< %{_libdir}/pgsql/slon-tools
---
> %{_libdir}/pgsql/slon-tools.pm
125a127,129
> * Tue Oct 31 2006 Trevor Astrope <astrope at sitesell.com>
> - Fixup tar name and install slon-tools as slon-tools.pm
>