directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bastiaan Bakker (JIRA)" <>
Subject [jira] Created: (DIRSERVER-749) fix issues with apacheds RPM to get it working out of the box
Date Fri, 22 Sep 2006 13:14:22 GMT
fix issues with apacheds RPM to get it working out of the box

                 Key: DIRSERVER-749
             Project: Directory ApacheDS
          Issue Type: Improvement
          Components: installer-plugin
    Affects Versions: 1.0-RC4
         Environment: linux
            Reporter: Bastiaan Bakker

The apacheds RPM has several issues that prevent it from running out of the box:
* the init script fails to run because APACHEDS_USER is set to $USER, which is not defined
at boot time
* the init script fails to run bevause JAVA_HOME is not defined
* the init script it is not registered to the init subsystem with chkconfig or similar
* the config files are not marked as such, causing them to be silently overwritten when one
upgrades the RPM
* the RPM filename is not conform conventions: ${name}-${version}-${release}.${arch}.rpm
* the location of the files (/usr/local/apacheds-1.0_RC4) is version dependent, making upgrades
cumbsome. The admin has to relocate the partitions and config files on every updgrade.
* the sources and docs are included in the rpm, even though they are not necessary for operation.

The RPM build mechanism for apacheds also has some issues:
* runs rpmbuild as root, which is frowned upon by RPM gurus for security and safety reasons.
* the generated src.rpm is not self contained, ie. one cannot do a 'rpmbuild --rebuild' with
* the sudo mechanism is totally unnecessary

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message