[Kolab-devel] Kolabd and perl-kolab maintenance

Stephan Buys list at codefusion.co.za
Thu Apr 22 16:37:01 CEST 2004

Ok, we have a bit of code (and a slight re-arrangement of perl-kolab) in the

The meta_data functionality allows us to add the following to the top of each
template file:

destination : @l_prefix@/etc/postfix/main.cf
diff_cmd : diff -q ${OLD_CONFIG_FILE} ${NEW_CONFIG_FILE}
on_change : @l_prefix@/etc/rc postfix reload

(normal template file contents go here)

This allows the daemon to iterate through all the template files, located under
/kolab/etc/kolab/templates and automatically detect what to do with each file.
If you then need to add something to be managed by the daemon all you have
to do is install the template file under /kolab/etc/kolab/templates and the daemon
itself will know where to copy it (destination directive) and what to do if the file
has changed (on_change directive).

We will merge this work into CVS in the releng and devel folders as discussed 

Sorry for the delay, we are just wrapping up the Kolab Webclient, expect a 
release announcement soon. (All the relevant work is now in Horde's CVS)

Kind regards,

On Thursday 22 April 2004 15:19, Steffen Hansen wrote:
> On Thursday 22 April 2004 08:24, Stephan Buys wrote:
> > Hi all,
> >
> > What will the process be for the maintenance and updating for the
> > above mentioned packages? I really want Code Fusion to stay involved,
> > especially Stuart, as it contains so much of his work.
> And we definitely want you guys to stay involved (!)
> > In the past we have always discussed major changes before we commit
> > them to CVS. Is this still in order? I dont want to hold up the
> > Kolab2 contract process, but I want to make sure that we stay on
> > track with each others designs, changes so that we can all continue
> > to use the code base.
> I will not make any major redesign of the perl-kolab packages. At most I 
> will add a thing here and there when I need a new template or need to 
> fix a bug or so.
> Do you have something major you want to commit?
> > One of the features that we have lying around, and would like to
> > merge into CVS is the template meta_data functionality as discussed
> > earlier this year, on the list.
> I having followed the lists closely until recently. What is this 
> meta_data template for?
> regards

Stephan  Buys
Code Fusion cc.
Tel: +27 11 391 1412
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za

E-mail Solutions, Kolab Specialists.

More information about the devel mailing list