directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-749) fix issues with apacheds RPM to get it working out of the box
Date Fri, 29 Sep 2006 16:03:51 GMT
    [ http://issues.apache.org/jira/browse/DIRSERVER-749?page=comments#action_12438738 ] 
            
Alex Karasulu commented on DIRSERVER-749:
-----------------------------------------

Bastiaan,

You're trying to do some good things here but you're doing several things at once.  IMO it
might be better if we tackled one issue of the RPM problem at a time with changes being clearer
especially with the patches you provide.  For example we can tackle the move to opt and make
the package relocatable.  Then we can focus on allowing it to run as apacheds user etc.  By
breaking appart each issue it's easier to swallow and we can have some discussion on each
matter.  Does this sound reasonable?  Perhaps we can break this issue up into several smaller
issues and have some dialog on each matter on the mailing list.  Cool?

BTW regarding the mina issue there is a dep on the concurrent backport package.  Perhaps maven
is not pulling that down.  Perhaps you can write to the list on the specific problem and it's
details so we can make sure the issue goes away for you.  Since RC4 mina has transitively
introduced this new dependency into ApacheDS. 

Also your excellent RPM enhancements can applied for 1.0.1 since we're starting to run out
of time now.  For now we can deal with these existing RPM issues  although they're a PITA.
 I really liked what you tried to do and want to make sure we get there.  However we can have
a bug fix release within weeks to incorporate these changes correctly.  There's no need to
rush.  

It's good to have you helping out since you seem to know about this business of building RPMs.
 I whipped together what you see in a rush and fell really short while doing it.  I'd love
to have you interacting with us and on the team.  Please keep up the dialog :).

Thanks much!!!

> 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
>             Fix For: 1.1.0, 1.0
>
>         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

        

Mime
View raw message