[DIRSERVER-749] fix issues with apacheds RPM to get it working out of the box

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0, 1.0.1
• Fix Version/s: 1.5.1
• Component/s: installer-plugin
• Environment: linux
• Assignee: Chris Custine
• Reporter: Bastiaan Bakker
• Created: 22/Sep/06 13:13
• Updated: 15/Feb/09 13:36
• Resolved: 09/Aug/07 06:52

Description

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 it.
• the sudo mechanism is totally unnecessary