Just thought I'd add something to my previous JPackage commentary
that I think is important.
Remember that JPackage only "supports" 1 version of something
per release.
I made a quick example saying that if Tomcat uses 1.5
and ADS uses 1.3, and JPackage supports 1.4 (And does not feel
like building 1.5 since it seems to work fine for both ADS
and Tomcat) 1.4 gets shoehorned in.
In this case I'm only talking about direct dependencies.
Indirect dependencies can have the same scenario.
So what got built using Maven on the Apache end,
can end up being wildly different once JPackage
provides a set of RPMs for it.
This means people could start posting questions on the
on the Users list regarding bugs that were introduced
by JPackage due to a switch in the ADS dependencies.
We should note this, in case bizarre questions regarding bugs
start showing up, and they can't be replicated on our end.
Cheers,
- Ole
Alex Karasulu (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DIRSERVER-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494305 ]
Alex Karasulu commented on DIRSERVER-749:
-----------------------------------------
NP Bastiaan, it's hard to align at times. Oh I did not know about the JPackage
rpm. Perhaps we need to look at that. None of us besides Ole have been in
contact with the JPackage folks. Perhaps you can point us in the right
direction so we can see and discuss what they have done.
BTW Chris Custine is now looking at rewriting some of the code in the daemon and installer modules to properly generate an RPM with scripts that actually work out of the box. He's primarily focused on the 1.5 branch and will be switching us over to use the Tanuki wrapper instead of jsvc and procrun. As for 1.0 I don't think it's worth mucking with.
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
