[Kolab-devel] steffen: utils/admin generatefb.php,NONE,1.1

[Richard Bos]

HI,

would it make sense to update the hardcoded paths to autoconf variables?  I am 
not sure about it, as there may not be too many non kolab installations in 
operation.  But the few there are should be able to run this script as well, 
isn't it?  I made a first attempt as shown below.

Op Wednesday 09 May 2007 01:45:32 schreef cvs at kolab.org:
> #!/kolab/bin/php -c /kolab/etc/apache/php.ini

@PHP@ -c @webserver_confdir@

> <?php
> error_reporting(E_ALL);
>
> $kolab_prefix = '/kolab';

$kolab_prefix = '@prefix@';
actually not needed, as it is taken care of by the autoconf tools

> $kolab_includepath =
> $kolab_prefix.'/var/kolab/php:'.$kolab_prefix.'/var/kolab/php/pear';
> ini_set('include_path', $kolab_includepath.':'.ini_get('include_path'));

$kolab_includepath = @phplibdir2@:phppeardir@;

or just
ini_set('include_path', @phplibdir2@:phppeardir at .':'.ini_get('include_path'));
and leave out the kolab_prefix and the kolab_includepath variable

> require_once($kolab_prefix.'/etc/resmgr/freebusy.conf');
require_once(@resmgr_confdir@/freebusy.conf');


..................
>     echo "\tsudo -u kolab-n ./generatefb.php [--help] [--imaphost=<imap
> hostname>] [--imapport=<imap port>] [--user=<manager user>]
> --password=<manager password>\n";


sudo -u @kolab_usr@ ./....

May this work like this?


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