Thoughts on the age-old cyradm thingie

[Paul M Fleming]

I've built an RPM for local use and use the following I've seperated the
admin stuff Cyradm included into a subpackage. I've just copied the perl
/ location specific stuff 


%install
make install INSTALLDIRS=site DESTDIR=$RPM_BUILD_ROOT
PREFIX=$RPM_BUILD_ROOT/usr
rm
$RPM_BUILD_ROOT/usr/lib/perl5/site_perl/5.6.0/i386-linux/auto/Cyrus/IMAP/.packlist
rm
$RPM_BUILD_ROOT/usr/lib/perl5/site_perl/5.6.0/i386-linux/auto/Cyrus/SIEVE/managesieve/.packlist


%files client
/usr/bin/cyradm
/usr/lib/perl5/site_perl/5.6.0/i386-linux/auto/Cyrus
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Cyrus
%doc /usr/man/man1/sieveshell.1.gz
%doc /usr/man/man1/installsieve.1.gz
%doc /usr/share/man/man1/*
%doc /usr/share/man/man3/*



Mika Iisakkila wrote:
> 
> Jay Levitt wrote:
> 
> > Thinking further about this, I no longer like my idea of a
> > separate --perl-prefix configure option, because if I do
> > "configure --prefix=/home/jay", I should reasonably expect that nothing is
> > being installed into sitewide libraries.
> 
> You're right there. Getting cyradm and the perl libraries to compile
> (and run) has been the single biggest pain in the ass I've had
> with the entire package -- so much that we had to ditch cyradm
> completely and use IMAP::Admin from CPAN. The C callback stuff is just
> too hard to compile correctly unless you also compile Perl itself,
> and makes it really difficult to keep Cyrus and everything
> in a simple self-contained package you'd be able to drop on a
> different machine from where you actually compiled it.
> 
> --mika