Summary | Have horde.schema delivered with the horde-framework files |
Queue | Horde Base |
Queue Version | 3.2.1 |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | ml (at) radoeka (dot) nl |
Created | 09/08/2008 (6141 days ago) |
Due | |
Updated | 09/12/2008 (6137 days ago) |
Assigned | 09/11/2008 (6138 days ago) |
Resolved | 09/11/2008 (6138 days ago) |
Milestone | |
Patch | No |
do. But it sounds like you do some stuff special enough that it
shouldn't be too hard for you to get the schema from Horde if you
really need it.
In any case, even if the schema may be used by some framework
libraries, the schema file, like any other backend script, has to go
into horde/scripts per Horde directory layout policies.
framework packages?
In a multiple ldap system setup, this may be needed.
The ldap master system holds all the data in the ldap directory. This
data may contain
horde application configuarion settings, although the horde
applications are running
on a different (ldap slave) server.
In this setup the ldap master has only the horde-framework installed,
while the
ldap slaves have horde-based as well.
State ⇒ Rejected
Priority ⇒ 1. Low
kolab framework packages?
I guess have to back to my drawingboard ;)
State ⇒ Feedback
framework packages?
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Have horde.schema delivered with the horde-framework files
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
libraries as part of the horde-framework package. Currently the file is
provided by the horde base package.
A project that I'm working on needs the ldap schema of horde (horde.schema).
This file is located in horde cvs at http://cvs.horde.org/horde/scripts/ldap/
As such it is delivered with the horde base. This package mainly consist of
files that are installed in a webserver's document root:
# rpm -qlp horde-kolab-3.2_rc3-20080707.ix86-debian4.0-kolab.rpm | cut
-d/ -f1-6| sort | uniq -c | sort -nr
3261 /kolab/var/kolab/www/horde
1 /kolab/var/kolab/www
1 /kolab/var/kolab/tmp
1 /kolab/var/kolab
1 /kolab/var/apache/log/horde
1 /kolab/var/apache/log
1 /kolab/var/apache
1 /kolab/etc/kolab/templates/horde-kolab-conf.template
1 /kolab/etc/kolab/templates
1 /kolab/etc/kolab
The project that I'm working on is kolab, as can be concluded from the
output above ;)
Kolab uses the horde libraries that are delivered by the horde
framework. This package provides files that are mainly located in
lib/php:
# rpm -qlp
horde-framework-kolab-3.2_rc3-20080405.ix86-debian4.0-kolab.rpm | cut
-d/ -f1-4| sed 's,bin/horde-.*,bin/horde...,' | sort | uniq -c | sort
-nr
893 /kolab/lib/php
17 /kolab/bin/horde...
4 /kolab/bin/script
2 /kolab/bin/scripts
1 /kolab/bin/vfs
For a kolab server that only requires the horde libraries (framework)
it is with the
current package layout required to install also the horde base package to
obtain the horde.schema.
As the kolab server is equipped with a webserver it means, that because of
horde.schema many (3000+) files are exposed to the webserver. If the
horde.schema
file would be moved from horde base to horde framework this would not happen.
Hence, is it feasible to have the horde.schema file be moved from the
horde base to
horde framework for reasons explained above?