You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Bastiaan Bakker (JIRA)" <ji...@apache.org> on 2006/10/02 19:12:26 UTC
[jira] Commented: (DIRSERVER-749) fix issues with apacheds RPM to
get it working out of the box
[ http://issues.apache.org/jira/browse/DIRSERVER-749?page=comments#action_12439228 ]
Bastiaan Bakker commented on DIRSERVER-749:
-------------------------------------------
Alex, thanks for the postive feedback on my RPM enhancements. I'm fine with having the changes go into a 1.0.1 release instead of 1.0 if that will be released soon anyway. Don't want to hold up 1.0 :-)
I'm not sure whether JIRA would be the best way to fix the RPM incrementally: all the small patches will depend on each other, making the order in which they are applied essential. Also at the intermediate steps the RPM would still not be usable, making testing difficult for interested people.
Would it be possible for me to commit changes to a subversion branch instead of submitting patches? I can commit small changes with explanation which will be easier to review than this single patch. Yet, I don't have to wait for each change to be merged into mainline before doing the next step. People interested in the end result can just check out the latest revision of the branch instead of waiting for it to appear in the mainline trunk.
As for the functional changes in the current patch: the patch allows configuration of the old location and running apacheds as root through entries in the pom.xml. So, if you like, you can still switch to the old setup....
For people wanting to try out the new RPM, I've published 1.0.0 prerelease RPMs at http://www.cryptoforge.net/unofficial/apacheds/prerelease/ . They have been tested to run out of the box on a Fedora Core 5 box with jpackage JDK java-1.5.0-sun-devel-1.5.0.07-1jpp.
Cheers.
> fix issues with apacheds RPM to get it working out of the box
> -------------------------------------------------------------
>
> Key: DIRSERVER-749
> URL: http://issues.apache.org/jira/browse/DIRSERVER-749
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: installer-plugin
> Affects Versions: 1.0-RC4
> Environment: linux
> Reporter: Bastiaan Bakker
> Assigned To: Alex Karasulu
> Priority: Minor
> Fix For: 1.1.0, 1.0.1
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira