[ http://issues.apache.org/jira/brows...243
6853 ]

Emmanuel Lecharny commented on DIRSERVER-749:
---------------------------------------------

Thanks Bastiann for this list of problem !

We definitively have to fix them. Let me just comment some of them :

* JAVA_HOME : it *must* be defined before the installation, because there is
 no simple way to find a JVM on a server (by no mean doing a 'find / -name j
ava" could be a solution). (The important word in this sentence is of course
 _simple_ 

* The location is not really important right now, because the package is not
 the last one. It's still a RC. Those RC are not supposed to be used in prod
uction, and it allows us to install a newer version without destroying the p
revious configuration file
(which is a very valid concern you raised in your point #4). A symlink could
 help for the release...

* Sources and help : yes, but when you launch the installer, you can avoid t
heir installation. May be we can generate a pure binary RPM ?

* Root : this may be a problem, as we need to install ADS as a service, with
 a default port value = 389 (< 1024)

Can I suggest you help us improving the packaging? We are not really Linux/R
PM gurus, so feel free to give us any advice and direction (even patches) wh
ich can be used to build a better RPM !

(and for those who use W$, mac and Solaris, any feedback will be warmly welc
omed !)

Thanks again for the time you spent on the packaging !

> 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
>         Attachments: apacheds-branch-1.0-server-installers-rpmfix.patch, a
pacheds-daemon-trunk-rpmfix.patch
>
>
> The apacheds RPM has several issues that prevent it from running out of th
e box:
> * the init script fails to run because APACHEDS_USER is set to $USER, whic
h 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 chkconfi
g or similar
> * the config files are not marked as such, causing them to be silently ove
rwritten 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 depen
dent, 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 n
ecessary 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 a
nd safety reasons.
> * the generated src.rpm is not self contained, ie. one cannot do a 'rpmbui
ld --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://iss
ues.apache.org/ji...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]