Shibboleth-IDP rpm packaging

[Cantor, Scott]

On 6/17/19, 1:38 PM, "dev on behalf of Philip Prindeville" <dev-bounces at shibboleth.net on behalf of philip.prindeville at gigamon.com> wrote:

> The "why" is: this is a set of requirements that got dumped in my lap 2 weeks ago to support SSO for an existing product
> (based on Centos 6.6).

Then the actual upstream project aside, you presumably are looking at a tightly controlled situation with the container nailed down and packaged already (or you'd have to include that piece too). Given that, you certainly have the control necessary, and it adds in the constraint that anything we screw up re: upgrades would be identified in testing and Q/A and dealt with via patches in the RPM/etc. to make sure the final result is cleanly going to stop, upgrade, restart to meet the RPM contract.

But anyway, the bottom line is I think you're looking at a scripted "RPM just does what our installer does, or runs it outright" kind of scenario, not a literal translation of all our files into an RPM-controlled package. I think that would be much harder to try to pull off.

-- Scott