[
https://issues.apache.org/jira/browse/DIRSERVER-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494301
]
Bastiaan Bakker commented on DIRSERVER-749:
-------------------------------------------
Hi Alex,
Sorry for not replying sooner, I've been on holiday.
We were going to do small incremental patches ( in so far possible) but neither
Emmanual or you had time at that time. Unfortunately now I have less time to
spend on apacheds (I'm mostly limited to spend time on this at work where other
projects have gotten more priority now) :-(
Also, in the mean JPackage folks appear to have RPMed apacheds-1.0 the proper
way (a self contained srpm that rebuilds from source). I haven't looked at it
yet though.
Maybe trying to get that packaging to apacheds-1.5 is more useful than patching
the original RPM hack.
Have apacheds people been in contact with jpackage folks about this?
> fix issues with apacheds RPM to get it working out of the box
> -------------------------------------------------------------
>
> Key: DIRSERVER-749
> URL: https://issues.apache.org/jira/browse/DIRSERVER-749
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: installer-plugin
> Affects Versions: 1.0.1, 1.0
> Environment: linux
> Reporter: Bastiaan Bakker
> Assigned To: Alex Karasulu
> Priority: Minor
> Fix For: 1.5.1, 1.0.3
>
> Attachments: apacheds-branch-1.0-server-installers-rpmfix.patch,
> apacheds-daemon-trunk-rpmfix.patch
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
