Create RPM with jpackage

• Key: DIRSERVER-765
• Type: New Feature
• Status: Closed
• Resolution: Won't Fix
• Priority: Minor
• Assignee: Chris Custine
• Reporter: Emmanuel Lecharny
• Fix Version/s: 1.5.1

Description

Ole suggest we can use jpackage to create RPM. Let's give this tool a try !

Comments

[Alex Karasulu]

Ole what's the status on the use of JPackage and our installer plugin?

[Emmanuel Lecharny]

It seems to be available soon, but right now, let's postpone it to 1.5.1

[Chris Custine]

I think we have decided not to do a full JPackage dependency in our distribution, but I am going to assign this issue to me so that I can review it later and close it when the new installers are finished.

[Ole Ersoy]

The thing about JPackage is that
they allow only one official version
of each library supported in each
JPackage release.

This means
that instead of having something
like a maven repository with
lots of different versions of the
same artifact, they have one version
of each artifact. This in turn of coarse
means that if Tomcat and ApacheDS
depend on a library artifact, but depend
on different versions, JPackage might
decide that it's OK to use
version 1.3.4 of the artifact for
both ApacheDS and Tomcat,
when the reality is that Tomcat was
built with version 1.4.0 and ApacheDS
1.5.0.

JPackage does have very good spec files though,
and highly skilled RPM packagers, so looking at their
spec files is very helpful.

[Chris Custine]

We need more control over our packaging and dependencies so we have decided not to implement this. Our RPM packages contain all jar dependencies.

[Emmanuel Lecharny]

closed