[Kolab-devel] Making perl-kolab a real library

Marcus Hüwe suse-tux at gmx.de
Thu Jul 12 13:00:34 CEST 2007


Hi,

On 2007-07-11 15:29:09 +0200, Gunnar Wrobel wrote:
> Hi!
> 
> perl-kolab is intended to be a Perl library and only installs files
> within your perl library location.
> 
> But for a library perl-kolab knows way too much:
> 
>  - it "knows" that there is a kolabconf program
>  - it also requires a sendmail binary with a fixed location
>  - it expects certain kolab configuration files in fixed locations 
> 
> In principle perl-kolab fully depends on the kolabd package at the
> moment. While kolabd also depends on perl-kolab.
> 
> I consider this a problem for both packaging and maintenance of the
> code and would like to split all unnecessary knowledge from the
> perl-kolab package into the kolabd package which would result in a
> real perl library.
> 
+1

> This would not only resolve the circular dependency but would also
> allow to get rid of the current configure script within perl-kolab so
> we can just use the standard perl mechanism for installing packages. 
> 
> I attach a patch that demonstrates the necessary changes roughly. It
> is only a draft and has not yet been tested.
> 
I just had a glance at your patch but the idea looks great! I really 
like it:)

> In addition I would like to split kolabconf into its own package. It
> is an important tool for the Kolab server and I think it makes sense
> to develop it also as a specific perl package with its own rpm.
> 
I like this too.

> I'd be happy about comments. If people agree I'd open a bug for this
> and slowly convert perl-kolab as described. 
> 
If you need help or some testers I'm willing to help!


Marcus




More information about the devel mailing list