[Kolab-devel] gunnar: server/perl-kolab/bin kolab_bootstrap.in, NONE, 1.1 kolabcheckperm.in, NONE, 1.1 kolabconf.in, NONE, 1.1 kolabdcachetool.in, NONE, 1.1 kolabd.in, NONE, 1.1 kolabpasswd.in, NONE, 1.1 kolabquotareport.in, NONE, 1.1 kolabquotawarn.in, NONE, 1.1 kolab_smtpdpolicy.in, NONE, 1.1 kolab_upgrade.in, NONE, 1.1

[Richard Bos]

Hi,

Op Friday 10 October 2008 16:22:07 schreef cvs at kolab.org:
> Update of /kolabrepository/server/perl-kolab/bin
> In directory doto:/tmp/cvs-serv20319/bin
>
> Added Files:
>         kolab_bootstrap.in kolabcheckperm.in kolabconf.in
>         kolabdcachetool.in kolabd.in kolabpasswd.in
>         kolabquotareport.in kolabquotawarn.in kolab_smtpdpolicy.in
>         kolab_upgrade.in
> Log Message:
> Merge all perl tools into the perl-kolab package.

why did this happen?  Don't belong those tools/scripts whatever to the kolab 
server?  Why should e.g. kolab_bootstrap.in be part of perl-kolab and not of 
the kolab server package?  If kolab_bootstrap.in is going to be rewritten in 
bash, ruby, python, should it than be moved to respectively bash-kolab, 
ruby-kolab or python-kolab?

With all scripts removed from the kolab package, the latter is now almost an 
empty package...

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.