Shibboleth-IDP rpm packaging

[Philip Prindeville]

Hi.

I was looking to do RPM packaging for EPEL6 and 7 (and CentOS 6 and 7), and decided to consult the archives for any wisdom.

I saw that Etienne brought up the subject in 2015 but it didn’t look like it moved towards an actual RPM, so I guess I’ll assume the mantle…

I’m not a Java programmer (no, I’m a C/C++, Perl, Bash, and assembler knuckledragger) but I do have RPM packaging background.

Can anyone walk me through the packaging process?

What usually happens in the Redhat/EPEL/CentOS universe is:

(1) Unpack tarball
(2) Apply distro-specfic patches (optional)
(3) Run package’s configure script (or automake/autoconf, etc)
(4) Compile
(5) Install into a temporary target directory
(6) Copy files from temporary install into RPM and attach meta-information from RPM’s .spec (automated step)

And then sit back and enjoy.

My understanding of Shibboleth is that it gets configured, then installed, then built/rebuilt in the target directory, which is almost the reverse of the traditional RPM packaging steps.

What efforts have been made to do RPM packaging that I can leverage and possibly complete?

Thanks,

-Philip


This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately delete it. If you are not the intended recipient, do not read, copy, disclose or otherwise use this message. The sender disclaims any liability for such unauthorized use. NOTE that all incoming emails sent to Gigamon email accounts will be archived and may be scanned by us and/or by external service providers to detect and prevent threats to our systems, investigate illegal or inappropriate behavior, and/or eliminate unsolicited promotional emails (“spam”).